Turns out the SELinux options were set to restrict HTTP from accessing the network so it could not bind to the local STUNNEL process.
httpd_can_network_connect --> inactive I updated the booleans.local file and now it works perfectly. httpd_can_network_connect --> active Thank you again. Blair Copeland >>> Jonathan Steffan <[EMAIL PROTECTED]> 11/15/05 10:54 PM >>> Your welcome. You might try system-config-securitylevel and edit the HTTPD settings. Try: Allow HTTPD cgi support. Allow HTTPD scripts to connect to the network. Allow HTTPD to support built-in scripting. Unify HTTPD handling of all content files. (maybe? try last) Unify HTTPD to communicate with the terminal. You can then use 'chcon' and 'ls -alZ' to help work with the SELinux permissions. Check your messages log to see the SELinux access denied messages to get a better understanding of what is going on in the background. This resource might help you use SELinux: http://fedora.redhat.com/docs/selinux-apache-fc3/ Cheers to Linux, Jonathan Steffan P.S. I think you need to restart for the changes by system-config-securitylevel to take effect. Blair Copeland wrote: >Thanks to the brilliance of Jonathan Steffan it turns out that Fedora 4 >has SELinux enabled by default. "Hello problem." > >Thank you sir and hopefully no one will waste thier time now. >I appreciate it Jon and I appreciate the list maintainers here. > >Sorry it turned out to be off topic. > >Blair > >
