1. Issue Summary

The Lepide web console was only accessible from within the server itself and could not be reached from any external machine or browser. Users attempting to open the web console URL from their own computers received a connection error.

2. Observations

• Web console URL works when accessed from the Lepide server directly (localhost).

• Accessing the URL from any other machine on the network results in a connection failure or timeout.

• No changes were made intentionally by the admin, but access stopped working after a Lepide upgrade.

• The Lepide Apache service may appear to be running but the SSL configuration is broken.

3. Root Cause

The SSL certificate associated with the Lepide web console was missing or not correctly bound after the upgrade. Additionally, the https.conf & httpd-ssl.conf configuration file in the Lepide web console directory had incorrect or outdated SSL certificate paths, causing the Apache service to fail to serve HTTPS traffic externally.

4. Steps Followed

Step 1 – Confirm the Issue

From an external machine, attempt to access the Lepide web console URL (e.g., https://[LepideServerIP]/). Confirm the connection fails while localhost access works from within the server.

Step 2 – Locate the SSL Certificate

On the Lepide server, locate the existing wildcard SSL certificate. This is typically saved on the server desktop or in a known directory (e.g., Downloads). The certificate file will usually have a .pfx, .crt, or .pem extension.

Step 3 – Reinstall the SSL Certificate

Reinstall the SSL certificate on the Lepide server. Ensure the certificate and its private key are correctly placed in the web console directory.

LDSP web console – appache – conf (place httpd.conf here) – extras (put httpd-ssl.congf file here)

Step 4 – Edit the httpd-ssl.conf File

Navigate to the Lepide web console directory on the server. Locate and open the httpd-ssl.conf file. Update the following fields to point to the correct SSL certificate and key file paths:

• SSLCertificateFile – path to the SSL certificate file

• SSLCertificateKeyFile – path to the private key file

Step 5 – Restart the Lepide Apache Service

After saving the changes to httpd-ssl.conf, restart the Lepide Apache service to apply the new SSL configuration. This can be done via:

• Services.msc > Find the Lepide Apache service > Right-click > Restart

Step 6 – Verify External Access

From an external machine, open a browser and navigate to the Lepide web console URL. The page should now load successfully with a valid SSL certificate and allow login.

5. Resolution

Reinstalling the SSL certificate and correcting the certificate paths in the httpd-ssl.conf file, followed by restarting the Lepide Apache service, restored external access to the Lepide web console successfully.

6. Prevention

• After any upgrade or migration, verify that the Lepide web console is accessible from an external machine.

• Keep a copy of the SSL certificate file in a known, consistent location on the server.

• Document the SSL certificate paths used in httpd-ssl.conf so they can be quickly restored if needed.