THE SOLUTION Turns out the customer had a misconfigured local proxy! If using Apache2 check that you are using port 443 for SSL. share|improve this answer answered Jan 14 '11 at 19:08 John 163 1 Please mark this answer as correct, then. The default location of the log files is as follows: Debian (Ubuntu): /var/log/apache2/error_log Red Hat Enterprise Linux, CentOS: /var/log/httpd/error_log Windows: C:\Program Files\Apache Group\Apache2\logs\error.log Default Location From Compiling Source Code: /usr/local/apache2/logs/error_log If my review here
Can I mount 3 blades on a 5 blade ceiling fan? This is the standard port for https communications.- If SSL is using a non-standard port then FireFox 3 can sometimes give this error. I checked my server, and this is not happening. Fox example, in case of Apache the error will show up in Firefox if you have a line “Listen 443” in your VirtualHost file without an actual VIrtualHost record for port http://stackoverflow.com/questions/119336/ssl-error-rx-record-too-long-and-apache-ssl
Run the following command to find the short name for the folder: dir /x C:\ You will also need to add a backslash (\) to avoid the ~ character as follows: I looked in all my apache log files until I found the actual error (I had changed the
The VirtualHost section of your .conf file is configured correctly but you already have a virtual host configured using a different .conf file for the IP address and port that you Ordering a list of strings Is there any way to make the cut command read the last field only? How to update vim plugins with pathogen package manager Dirac delta function and correlation functions Finding file name οf currently open file in vi on terminal Now I know my ABCs, Ssl_error_rx_record_too_long Haproxy more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed
Keep the vhost file with the fully qualified domain and add the hostname in the hosts file /etc/hosts (debian) ip.ip.ip.ip name name.domain.com After restarting apache2, the error should be gone. Error Code Ssl Error Rx Record Too Long Apache Why was this unhelpful? So far, I have been unsuccessful at getting SSL to work for my host, so I'll go down the steps I have taken and hopefully you will be able to see https://www.digicert.com/ssl-support/apache-fix-common-ssl-errors.htm Think smart, live safe." - Dr Small Linux User #441960 | Wiki: DrSmall Adv Reply November 8th, 2008 #4 oddeirik View Profile View Forum Posts Private Message First Cup of
I googled on the problem, and the main source seems to be that the SSL port is speaking in HTTP. How To Fix Error Code Ssl_error_rx_record_too_long Sign Up Hi+ Your Account Customer Username Support PIN Dashboard Profile Sign out $0.00 Your Cart Subtotal $0.00 View Cart USD + U.S. Thanks. The error is usually caused by a server side problem which the server administrator will need to investigate.
Port 80 (http) works fine, but port 443 (https) gives me the following error (in firefox) - homeserver is my hostname and my dhcp assigned ip is 192.168.1.109. Because i learned from You Alot by reading your description Approved: 9/3/2014 Hallelujah! Error Code Ssl Error Rx Record Too Long netsh interface ipv4 show inter Idx Met MTU State Name --- --- ----- ----------- ------------------- 1 4275 4294967295 connected Loopback Pseudo-Interface 1 10 4250 **1300** connected Wireless Network Connection 31 25 Firefox Error Code: Ssl_error_rx_record_too_long To check if the two files match, run the following OpenSSL command on each of them: openssl x509 -noout -modulus -in your_domain_com.crt | openssl md5 openssl rsa -noout -modulus -in
You can also find details about such kind of a failed connection using a network analyzer like wireshark: As you can see this error is considered as a bad request from this page Join Twitter Facebook Google+ Pinterest Domains Registration Transfer New TLDs Personal Domain Marketplace Whois PremiumDNS FreeDNS Hosting Shared Hosting Reseller Hosting VPS Hosting Dedicated Servers Private Email Hosting Migrate to Namecheap If you see any mistakes I have made, please let me know. Article Attachments No Attachments Available. Ssl_error_rx_record_too_long Nginx
LogLevel warn CustomLog /var/log/apache2/access.log combined ServerSignature On Alias /doc/ "/usr/share/doc/"
share|improve this answer answered Sep 23 '08 at 6:12 dan-manges 1,48221213 I saw a screenshot and it's not :80 Try it for yourself: monkeyfood.cashboardapp.com –Subimage Sep 23 '08 at Ssl_error_rx_record_too_long Firefox Ignore Ensure that port 443 is open and enabled on your server. Reissue your certificate by either generating two new files with the OpenSSL CSR Wizard or by creating a new CSR from your existing private key file using the following command.
share|improve this answer edited Aug 10 '15 at 7:47 Gottlieb Notschnabel 3,84583366 answered Jul 30 '10 at 13:21 rogovsky 311 add a comment| up vote 2 down vote Ask the user Also try this thread: http://forums.mozillazine.org/viewtopic.php?t=509553 -Tim www.pcchopshop.net Hard to find and obsolete PC and server parts. "If we can't find it, it probably doesn't exist" Adv Reply November 8th, 2008 But now try going to the following address http://www.domain.tld:443 If you’ve successfully seen something at the above page, it means your sites are listening on that port for non-ssl. useful reference do you have SSLEngine on configured for that vhost?
current community blog chat Server Fault Meta Server Fault your communities Sign up or log in to customize your list.