WordPress can't interact correctly with the file system

[Nate Reist]

We are having issues with WordPress sites being able to write to the file system (uploads, plugins & theme updates/installs, configuration file modifications). This problem started this week, and the permissions on the files are set to 644 (and 755 for directories). The issue is consistent among all sites on the server.

We are running CentOS 7 WHM 96.

The only thing that we have changed recently is the server was set to allow remote domains this week (which it hadn't needed to be in the past).
WP CLI can still modify files properly.

Any ideas what would be causing PHP over http to not be able to write?

 

[cPJustinD]

Hello Nate Reist! Given the information provided in the forum thread you originally reported this issue in, I think it would be best to open a support ticket so that our analysts can review the issue more thoroughly and determine what exactly is occurring. You can submit a support request using the "Submit a ticket" link in my signature below.

Please be sure to link this thread when opening the ticket and provide the ticket number here so that we can track the issue appropriately. If possible, please post the resolution on this thread as it may help other community members with similar issues.

 

[Nate Reist]

Hey @cPJustinD

Success! Here was the ticket number: #94334605, but the articles after the submission resolved the issue (so I closed the ticket). Specifically this article was the fix, I activated mod_suexec, which fixed this issue. This doesn't answer to me why this problem would just have arisen, it would be nice to find that so we can understand what changes caused this issue.

 

[cPJustinD]

I'm glad to hear that the article provided was able to help you resolve the issue! Since the ticket has been created, our analyst should be able to connect to the server. I would suggest replying to the ticket inquiring about the root cause. Determining the root cause of the issue may be difficult, although I still feel it may somehow be related to the recent changes we rolled out to EasyApache as we discussed in the original thread.