tinsleyjr

Thank you toddalancox. You got me on the right track. I wasn’t able to use the --type option with chconu since, I guess, it wasn’t in my SELinux policy. I kept getting “Invalid Argument” whenever I ran that command. Instead I had to reference my wp-content directory that had the httpd_sys_rw_content_t type. I used this command to get it to work sudo chcon --reference=/var/www/html/wp-content -R /var/www/html/. Thank you all for your help.

Well…, I ended up finding out what my issue was, I had to temporarily disable SELinux. I still need to figure out how to avoid having to disable SELinux each time I need to update, but running two simple commands over manually updating my site is much easier. If any of you have any insite into why SELinux was my problem, or how to configure SELinux that would be much appreciated. I’ll leave this post up for a little while before I mark it as answered to see if anyone has a response to the SELinux issue.

I appreciate everyone’s input on this matter.
@claytonjames I tried setting the SE configuration you mentioned, but unfortunately, that did not solve my issue. I have wordpress installed to the root of my html directory (i.e. /var/www/html) and ran these two commands on that directory

> find /var/www/html -type f -exec chmod 664 {} \;
> find /var/www/html -type d -exec chmod 775 {} \;

According to everything I have read, my permissions on my wordpress should be configured correctly.

Furthermore, I verified what httpd is running as and, as of right now, I have the owner:group for the files and directories in /var/www/html configured for the account used by httpd.

The screwy thing is as I mentioned in my first post, when I set the permissions temporarily to 777 I still get the error. I know I’m missing something, I’m just not sure where.

That worked! Thank you so much for getting back to me and my apologies for the late response.