Resolved What can I do to update permissions following a directory change?

[Chad]

Hello,

*Updating to a new subject here - as put in the incorrect name...my apologies.

After moving sites from initial default directory to a new /home directory - there are certain permission errors happening following creating new WordPress sites.

Here is some errors showing up in the logs now:

527404#0: *411098 openat() "/home/vhosts/......../httpdocs/wp-admin/images/spinner.gif" failed (13: Permission denied)"
527404#0: *411773 openat() "/home/vhosts/......../httpdocs/wp-includes/js/admin-bar.min.js" failed (13: Permission denied)
527404#0: *411931 openat() "/home/vhosts/........./httpdocs/wp-content/uploads/2017/04/.....logo-300x97.png" failed (13: Permission denied)

After trying to reset permissions and seeing existing sites work just fine I'm at a loss of what is required to correct permissions, so new sites get the proper permissions automatically.

Any insight would be much appreciated.

Thank you,

 

[IgorG]

Just use plesk bin transvhosts.pl utility for changing default vhosts directory location.

 

[Chad]

Thanks, I had used this very step to make the move, this seemed to go just fine - until creating new WordPress sites.

New sites created prior worked with no permission errors, after the move the errors began.
Any thoughts on what could be the solution?

 

[IgorG]

Maybe SELinux issue? Anyway, plesk repair fs also would be useful.

 

[Chad]

Using repair with fs or web both come back with no errors, mentioning all is 'ok'.
Only the logs show the permission error, what could be causing the repair tool to see all is good yet the error to remain?

 

[Chad]

Okay, after looking through the logs all errors related to nginx.

When proceeding to apache & nginx settings and turning off smart static files processing - all errors cleared, site performs beautifully now.

What could be causing nginx permission errors?

 

[IgorG]

What is output of

# getenforce

?

 

[Chad]

output mentions disabled

 

[IgorG]

Maybe it was enabled before? This looks very similar to this case - Configuration errors are shown after subscription creation. Apache failes to start due missing logs

 

[Chad]

Indeed a similar error, just on nginx.

Not sure if it was enabled, no changes and from the information in that link - it looks that disabled mode is the only way this will work. Which should mean we are good here, as the feature is disabled - similar but different, what could be causing this problem. Looking through many related posts point to a permission issue not allowing nginx to read the file, which is the experience here. Once the files/images....can be read the site works just fine - just not sure what to set so nginx can read the files.

 

[Chad]

So, adding nginx to the group psacln cleared all errors except for reading .jpg files.

Any thoughts on what's missing for reading .jpg?