Twitter TweetsRecent FAQ'sMailing ListNewsAzerTech.net News FeedThe Software Development Cycle When BNT Solutions (http://www.bnt-solutions.net/) was incorporated in 2001 there was one goal in particular that ran as a thread through... Introduction to Networking The very first time I tried to setup a server at home I discovered something unexpected: What I thought was going to... Subscribing to a Mailman list from any web page It happens quite often that you want people to be able to subscribe to your Mailman mailing list from a... Montreal Family Time for Canadians to speak! The Government of Canada has begun a nationwide series of consultations on copyright modernization. Linked-In for business and pleasure The Linked-In crowd will try to convince you that their service is good for business. This is more... A sad day for free speech and copyright law Here is some important, well written commentary from William Patry and, in response, Pamela Jones of Groklaw. First, illiam Patry explains why he... |
Strange error messages when connecting to a virtual host via SSL
While trying to connect to an Apache virtual host via SSL, the browser keeps returning very strange error messages like ...unsupported SSL version... or ...site returns an unexpected error code.... What's going on?
Normally when we create a new virtual host for Apache, we don't bother to copy all the settings from httpd.conf. This is because Apache takes the base setup of the server as a default configuration. Each virtual host definition, therefore, is only specifying those configuration details that have changed from the default (like ServerName and DocumentRoot.) As such, we are accustomed to writing very short virtual host definitions.
Sadly, this doesn't work quite as well when creating SSL-based virtual hosts. Some of the settings that we assume will become defaults - don't! If you get strange error messages when connecting to your SSL-based virtual host, it's probably because you need to copy some of the details in conf.d/ssl.conf to your virtual host definition. Here are the ones that tripped me up recently: Once I realized that this was an issue I just copied out all the active lines from conf.d/ssl.conf - probably a bit of overkill. Still, it solved the problem. That being said, there's no solution more effective than reading the docs to avoid trouble in the first place. Diligent admins will refresh their memories by reviewing the docs (something I failed to do recently... hence this note!) Documentation for the SSLEngine directive is here. Don't forget to review the Apache mod_ssl FAQ.
|

