Difference between revisions of "Apache2 Invalid method in request \x16\x03\x01"

From Noah.org
Jump to navigationJump to search
(New page: Category:Engineering Category:SSL This error is due to a misconfiguration of VirtualHost with SSL. The server is trying to respond to a request on port 443 with unencrypted HTTP. ...)
 
Line 18: Line 18:
  
 
Almost certainly the problem is that your server is using this default or the server is not matching your virtual host's IP at all. For SSL to work you <em>must</em> match the virtual host by <em>IP address</em> not name. [Apache2_mod_vhost_alias_ssl|Named virtual host won't work with SSL].
 
Almost certainly the problem is that your server is using this default or the server is not matching your virtual host's IP at all. For SSL to work you <em>must</em> match the virtual host by <em>IP address</em> not name. [Apache2_mod_vhost_alias_ssl|Named virtual host won't work with SSL].
 +
 +
== could not bind to address 0.0.0.0:443 ==
 +
 +
If you get this error on startup then it means that you a configuration problem where the server is trying to listen on all interfaces on port 443 and you have told it to listen to port 443 on a specific interface.
 +
 +
<pre>
 +
Address already in use: make_sock: could not bind to address 0.0.0.0:443
 +
</pre>
 +
 +
Probably you have a section with a specific VirtualHost IP address conflicting with the _default_ VirtualHost. A section something like this "<VirtualHost 192.168.0.1:443>" cannot be used with the default section like this "<VirtualHost _default_:443>".

Revision as of 17:39, 7 August 2008


This error is due to a misconfiguration of VirtualHost with SSL. The server is trying to respond to a request on port 443 with unencrypted HTTP.

Typically your conf/httpd.conf file will include conf/extra/httpd-ssl.conf:

Include conf/extra/httpd-ssl.conf

The default httpd-ssl.conf file will have a section like this:

<VirtualHost _default_:443>
...
</VirtualHost>

Almost certainly the problem is that your server is using this default or the server is not matching your virtual host's IP at all. For SSL to work you must match the virtual host by IP address not name. [Apache2_mod_vhost_alias_ssl|Named virtual host won't work with SSL].

could not bind to address 0.0.0.0:443

If you get this error on startup then it means that you a configuration problem where the server is trying to listen on all interfaces on port 443 and you have told it to listen to port 443 on a specific interface.

Address already in use: make_sock: could not bind to address 0.0.0.0:443

Probably you have a section with a specific VirtualHost IP address conflicting with the _default_ VirtualHost. A section something like this "<VirtualHost 192.168.0.1:443>" cannot be used with the default section like this "<VirtualHost _default_:443>".