Hmm, disabling SELinux enforcement with 'setenforce 0' (option C) seems like a quick fix, but it's not the most secure approach. I'd stick with B to keep things locked down.
Whoa, looks like a permissions issue with the Apache server and the database connection. I'd go with option B, 'setsebool -F httpd_can_network_connect_db on' to safely enable the connection.
Jutta
10 minutes agoSue
9 days agoReta
13 days agoErasmo
13 days agoSue
16 days ago