Troubleshooting TLS Certificates

TLS on Router

The TLS certificate associated with the ticketing site may not always be the only TLS certiificate in the network. The TLS certificate in Nginx may have installed correctly without error or warnings. The web pages appear correctly within the network. However, when attempting to access the site externally, the web pages do not display. The web site looks like it may be pointing to IIS or another application. The network setup will appear correct and everything on the Web Server machine is running. Reviewing a test of the TLS Certificate does not display the Comodo Logo.

In this situation an TLS may be built into the router. The IT person will need to locate the TLS Certificate and disable it.

TLS doesn't appear on HTTP

When visiting the ticketing site the address starts with http rather then https. The style sheets are missing and the buttons do not appear.

This is caused by a missing S from https in the Web Server URL field under the Director tab of Setup >> Company Preferences.

The site can be accessed using https but not http

When accessing the ticketing site using http rather then https the Web Pages are not displayed. The ticketing site is replaced by another website, application or login. The link will not redirect to https automatically but rather needs to be altered to include the S.

Port 443 governs https by default. Port 80 is reserved for http. Some organizations use port 80 for other applications such as web mail. In cases like this all direct links to the ticketing site will need to start with https.