Hey all,
I’ve been working on a droplet developing a small WordPress site on CentOS 8. Early on in development, I set the SELinux boolean httpd_can_network_connect to true as I was experiencing problems updating themes and plugins and all was fine. I haven’t logged in in around 3 weeks or so, but when I did today I noticed the same issues I was experiencing before I set the SELinux boolean and some errors in the WordPress site health menu. After investigating, I noticed the boolean somehow got set back to false. I used sudo setsebool -P httpd_can_network_connect true once again and everything went back to normal. Can anyone tell me when might have caused an SELinux boolean to reset, despite me not signing in/working on anything?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi, I have never met the situation like that. Did you set this boolean up permanently (with -P parameter) when you did it for the first time ? Search for a related command in bash history file:
grep -e httpd_ ~/.bash_history
If not, then following system reboot restored the previous value.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.