JoeM
05-14-2001, 05:45 AM
This one has had me going for over a week now:
I do a self signed cert via the RaQ4i control panel.
Then when trying to access my domain via https://www.mydomain.com, Internet Explorer just hangs forever, and Netscape says, "server refused connection".
HOWEVER, when I go to admin via http://www.mydomain.com/admin the page WILL go secure by flipping to https://www.mydomain.com:80/admin and Netscape will go through the usual "New Site Certificate" warnings, etc. Indeed both browsers behave as expected with a self-signed cert, BUT, only by accessing /admin as opposed to accessing any other address via https:
It seems like there is some wrong in the httpd.conf file that is aiming the SSL stuff one level lower (i.e. port 80) instead of securing any publicly accessable directory.
At this point I don't want to go out and buy a cert when the server is acting this way.
Does anyone have a clue as to what could be wrong?
Thanks,
Joe
I do a self signed cert via the RaQ4i control panel.
Then when trying to access my domain via https://www.mydomain.com, Internet Explorer just hangs forever, and Netscape says, "server refused connection".
HOWEVER, when I go to admin via http://www.mydomain.com/admin the page WILL go secure by flipping to https://www.mydomain.com:80/admin and Netscape will go through the usual "New Site Certificate" warnings, etc. Indeed both browsers behave as expected with a self-signed cert, BUT, only by accessing /admin as opposed to accessing any other address via https:
It seems like there is some wrong in the httpd.conf file that is aiming the SSL stuff one level lower (i.e. port 80) instead of securing any publicly accessable directory.
At this point I don't want to go out and buy a cert when the server is acting this way.
Does anyone have a clue as to what could be wrong?
Thanks,
Joe
