Web Hosting Forum | Lunarpages

Author Topic: https not working?  (Read 1446 times)

Offline marylockman

  • Newbie
  • *
  • Posts: 3
https not working?
« on: April 01, 2017, 07:37:11 AM »
My https://www.methowrealestateservices.com site is not working. I followed all the instructions, and according to help ticket lunar pages has installed the ssl certificate and given me a dedicated IP address. I do not know what else to do to get this to work?  It has been many hours since LP said it is working.
Unfortunately the phone support is not up and running on weekends. Boo. http://www.lunarforums.com/Smileys/default/help.gif

Offline marylockman

  • Newbie
  • *
  • Posts: 3
Re: https not working?
« Reply #1 on: April 01, 2017, 08:27:10 AM »
Here is what I googled from firefox results:
After installing the SSL certificate, the following error appears when connecting to the server using Firefox:

Secure Connection Failed

An error occurred during a connection to <server-name>.

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)

The web server is sending non-secure (HTTP) data where secure (HTTPS) data is expected by Firefox. This can be confirmed by going to http://server-name:443 instead of https://server-name.

Check the configuration of the server to ensure that SSL has been configured correctly. This most commonly occurs when using Apache or Tomcat as the web server, though it can certainly occur in other server types. Points to consider when troubleshooting this error in either Apache or Tomcat:

In Apache, check that the Listen <port> directive matches the port number in the VirtualHost directive for the website being secured, and that the SSL configuration statements (SSLEngine On, SSLCertificateFile <filename> and so on) appear in the VirtualHost directive for the website or in the SSL configuration file for the server.

In Tomcat, check that the connector in server.xml is configured to use SSL (there should be scheme="https" secure="true", as well as keystoreFile and keystorePass statements) and that the port number listed in the connector is what is expected -- if using the default port (8443), it needs to be specified as part of the URL or be appropriately redirected on the server. Tomcat may also be switching to non-secure mode for a connector where the keystore is corrupt; try creating a new keystore and replacing the SSL certificate.


Offline MrPhil

  • Senior Moderator
  • Berserker Poster
  • *****
  • Posts: 6264
Re: https not working?
« Reply #2 on: April 02, 2017, 05:16:05 AM »
Is it still not working? I brought up your site, and it is OK in https. Perhaps your browser still has a cached version in it -- hit Ctrl-F5 to force a refresh.

I do get a warning that many links and resources on your page are still http:. You will need to fix the page source to use https:. Also, you have a logo in your slide show which is magnified way too much, and thus very poor quality.

By the way, support is still accessible on weekends via email or ticket system, even though telephone support is not open.
Visit My Site

E-mail Me
-= From the ashes shall rise a sooty tern =-


Share |