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
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 wit
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
Fedora 4 has SELinux enabled by default. This might be an SELinux issue.
Run the following command to test without SELinux:
#setenforce 0
If that fixes it, you need to tweak your SELinux settings for Apache.
You can email me for help if needed. Fair warning, reboot or 'setenforce
1' because y
