Updating SSL Certificate on Captive Portal for Wi-Fi Connectivity

Overview

This article discusses the resolution of Wi-Fi connectivity issues related to an expired SSL certificate on a captive portal, affecting user access and revenue.

Solution

1. Identify the Certificate Issue: Recognize the problem with the SSL certificate.
2. Ensure Certificate/Key Files and the conf files are provided: Request necessary files from the client - the certificate and key files along with the httpd.conf file.
3. Check httpd.conf File: Match certificate names with the server's configuration.
4. Coordinate with the Client: Facilitate the update process through client collaboration.
5. Update the SSL Certificate on the Server:
   • Ensure that the new filenames match the old ones at /etc/https.
   • Take backups of the existing files.
   • Replace old files with the new ones /etc/httpd.conf
6. Restart Services if Necessary: Restart server services to implement the new certificate.
7. Verify Portal Accessibility: Confirm the portal's functionality post-update.

Summary

The article provides steps to update the SSL certificate on the captive portal server.

FAQ

1. How do I know if my captive portal's SSL certificate needs updating?

If users are unable to see or connect to the portal, an expired SSL certificate may be the cause.

2. What files are needed to update the SSL certificate on a server?

Both the SSL certificate file and its corresponding key file are required for the update.

3. How can I confirm that the new SSL certificate is working correctly?

Verify the portal's accessibility on different devices and ensure that functionalities like OTP generation are operational.