On 6/30/06, Bill Habermaas <bill@xxxxxxxxxxxxx> wrote:
Interesting results. Netstat says apache is listening on 443. If i telnet using 127.0.0.1 from the same machine it connects. If I telnet from another machine behind the same firewall it fails with connection refused. The other machine is freebsd with Apache SSL and it can be accessed via HTTPS from outside the firewall with no problem. So it looks like Apache is binding 443 to the local address, I didn't tell it to do that. Bill ----- Original Message ----- From: "James Kosin" <jkosin@xxxxxxxxxxxxxxxxxx> To: "For users of Fedora Core releases" <fedora-list@xxxxxxxxxx> Sent: Friday, June 30, 2006 10:20 AM Subject: Re: Apache SSL not working > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Randy Wyatt wrote: >> On 6/30/06, Bill Habermaas <bill@xxxxxxxxxxxxx> wrote: >>> >>> >>> Has anyone had problems getting Apache SSL working on FC5? >>> >>> I have a Dell PowerEdge 1750 with FC5, Apache 2.2.0. I have tried >>> everything to get HTTPS to work without success. HTTP works >>> fine, no errors in any of the logs, but HTTPS urls just hang and >>> eventually timeout with a page not found. No errors appear in >>> the Apache SSL logs either. I have removed Apache entirely and >>> reinstalled with YUM but still encounter the same problem. I >>> have FC5 running on a laptop and it works just fine (same version >>> of Apache) and the configuration files have been compared >>> line-by-line for errors or typos. I even tried different SSL >>> certificates to no avail. Now I am wondering if it something to >>> do with the hardware. I'm out of ideas on what else to check. >>> >>> Any feedback would be appreciated. >>> >>> Bill -- fedora-list mailing list fedora-list@xxxxxxxxxx To >>> unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list >>> >>> >> >> Have you tried telnet www.servername.com 443 >> >> and see if the socket connects. Are you using anything like NIS, >> what is in your /etc/services file? >> > No, first check the firewall settings. Be sure he has port 443 open > to the outside world. > Using telnet will only give you identical results... But, to be sure, > you can use telnet on the local machine to check to see if HTTPS is > working by using 127.0.0.1 or localhost.localdomain as the server name. > > In 99% of the cases though, it will be the firewall blocking port 443. > > - -James > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFEpTNCkNLDmnu1kSkRAh8+AJ9tFo879LXXEDa9hHP6e0dtbLOTRQCeLusk > Nryn2AFpe89J+l3/I+jLNQ4= > =NQtg > -----END PGP SIGNATURE----- > > -- > Scanned by ClamAV - http://www.clamav.net > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > > -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Actually, you still have a local firewall that has to be configured to allow incoming 443 connections. You can get to it through the menu screens. My FC5 box is getting rather lonely at work!
