Quick update: Upon being onsite with my server, the HTTPS works internally using the server's internal network IP, just get a certificate error becuase of the name mismatch(using the internal IP instead of the domain). I've looked over this so much, and I am still lost. Hoping that insight may help. Chris On Feb 22, 2016 10:24 AM, Sander Smeenk <ssmeenk@xxxxxxxxxxxx> wrote: > > Quoting Stormy (stormy22@xxxxxxxxx): > > > FWIW using Firefox 38.3 ESR, your login page works on port 80; forcing https > > results in: "Secure Connection Failed An error occurred during a connection > > to tracss.adamstelecom.com. SSL received a record that exceeded the maximum > > permissible length. (Error code: ssl_error_rx_record_too_long)" > > The webserver behind tracss.adamstelecom.com is talking plain HTTP on TCP/443. > > | % telnet tracss.adamstelecom.com 443 > | Trying 68.187.20.120... > | Connected to tracss.adamstelecom.com. > | Escape character is '^]'. > | GET / HTTP/1.0 > | > | HTTP/1.1 301 Moved Permanently > | [ .. ] > > Probably missing 'SSLEngine On' for the correct vhost(s). > > -Sndr. > -- > | Showering in clothes shows you're crazy. Showering nude shows your nuts. > | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|