Technical Tip: EMS-Failed to load URL https://localhost/ with error ERR_CONNECTION_REFUSED (-102)

[JBarrera]

Description	This article describes how to solve the EMS error on Premise: Login  ERR_CONNECTION_REFUSED (-102).
Scope	FortiClient.
Solution	EMS error shows: Try to restart the FortiClient Endpoint Management Server Apache Service from Windows server 'Services' services.msc. Sometimes the service cannot be restarted. Run the command 'net stop http' and then start the Apache service again in the task manager. The EMS Web Page should responds. If still same issue, it is possible the Apache Service will show error below when trying to be started: To confirm the issue, collect and check the Apache logs in FortiClient EMS diagnostic tool. Technical Tip: How to collect FortiClient EMS on-premise logs by Diagnostic tool. A similar error as below should be found: ..AH025XXX: Certificate and private key localhost:443:0 from C:/Program Files (x86)/Fortinet/FortiClientEMS/Apache24/conf/ssl.crt/FCTEMSTA200XXXX.1.cert and C:/Program Files (x86)/Fortinet/FortiClientEMS/Apache24/conf/ssl.key/FCTEMSTA2000XXXX.1.cert.key do not match AH00016: Configuration Failed If the log record is confirmed, this issue is caused by certificates/keys being mismatched in the database and filesystem.  A hot-fix can be applied to restore Apache Services. Next step is to contact TAC Support to receive the hot-fix solution.