Anyone know if SELinux is responsible for the .htaccess issue as well? Haven't corrected that part of my problem yet. Thanks, Jacques B. On 3/22/06, Jacques B. <jjrboucher@xxxxxxxxx> wrote: > Found the problem. SELinux was the problem. Found the solution at > http://72.14.203.104/search?q=cache:epnbAX_bGy8J:blogs.redhat.com/fedora_blogs/FEDORA_BLOGS.html+fc5+httpd.conf+Listen&hl=en&gl=ca&ct=clnk&cd=3 > > Notice it's in Google Cache as the posting no longer exists on the > page in the link provided by the search hit. > > By the way is this getting out to the list? Didn't see my original > posting come through, and no replies which I was suprised given how > active this list is. > > Thanks, > > Jacques B. > > On 3/22/06, Jacques B. <jjrboucher@xxxxxxxxx> wrote: > > I did a fresh install of FC5 on my web server (was FC2, now FC5). I > > was previously using two Listen commands in the httpd.conf file (just > > ports i.e. > > > > Listen 80 > > Listen 443 > > > > And I was using .htaccess & .htpasswd for access control to a site on port 80. > > > > However I get a Failed when trying to start the httpd with another > > Listen command in the conf file. At startup the error was something > > like it couldn't bind to 0.0.0.0:443. > > > > And the .htaccess is not prompting for a password. I've gone over the > > old .conf file that I had saved and the new one and can't see anything > > that I'm missing. I have the Virtual Host commands, and the > > NameVirtualHost *:80 as well as a second such command for the > > alternate port. And I've opend up those ports in iptables (which > > wouldn't affect starting the httpd, it would only affect connecting to > > it, but just to make sure...) > > > > Any idea what might be causing this problem? I've re-booted a number > > of times just to be certain. If I comment out the second Listen > > command (which is on its own line, and I use vi to do all my editing), > > it works. But if I put in the second Listen command regardless of the > > alternate port, httpd fails to start. > > > > By the way where could I go to see the errors produced on startup? I > > checked /var/log/messages and dmesg but couldn't find the error > > message generated on bootup when trying to start the httpd. When > > trying to start it afterwards using /etc/init.d/httpd start, it simply > > says failed. Could I make that more verbrose? Couldn't find any > > switches in the man pages that would do that. > > > > Thanks, > > > > Jacques B. > > > -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
