Skip to content

HTTPS quick configuration wizard

ARTICLE TYPE
How To

TITLE

HTTPS quick configuration wizard (Safekit Console)

ANSWER

To re-enable the HTTP protocol for the unsecure SafeKit web console after another configuration disabled it, remove the file SAFE/web/conf/ssl/httpd.webconsolessl.conf and restart the web server.

Product:
Safekit

connection error signals a connection failure with the node. Once the connectivity problem is fixed.

Connection issues with the web console If you encounter problems for connecting to the SafeKit web console to SafeKit node, such as no reply or connection error, run the following checks and procedures: - Browser check Chrome or IE

  • Browser state clear -- Clear the browser cache -- Clear the browser SSL cache if HTTPS is used --- Look at advanced settings for the browser and search for SSL cache

  • Server check -- The safeadmin and safewebserver services are started on the server -- safekit cluster confinfo

Check all certificates

On each SafeKit nodes: Log as administrator/root and open a command shell window Change directory to SAFE/web/bin 

Run checkcert -t all
It checks all installed certificates and returns a failure if an error is detected You can check that the server certificate contains some DNS name or IP address with:

checkcert -h ”DNS name value”
checkcert -i ”Numeric IP address value”

The server certificate must contain all DNS names and/or IP addresses used for HTTPS connection. These ones must also be included into the SafeKit cluster configuration file.

Related articles: