Resolved Permissions issues after running `plesk repair all -y`

[Mathijs]

While running `plesk repair all -y` I got the error as seen below.

This caused the Wordpress website on there to give the Forbidden error. Which I am unable to solve by the usual ways (delete htaccess, disable plugins), including restoring a backup from yesterday.

Does anyone has any clue as to what I should do now?

Thanks so much in advance!

 

[Brujo]

sounds like broken ownership, take into consider to show how the structure and ownership/permissions of /var/www/vhosts/yourdomain/httpdocs looks now on your system

there should be also some details in the domain errorlog /var/www/vhosts/yourdomain/logs/

see also: Unable to open some pages or files inside a domain: 403 Forbidden and [HUB] 403 Forbidden

 

[Mathijs]

Thanks for the quick response.

While checking the Wordpress Toolkit I got an security message for the permissions of all my Wordpress installations, which I fixed via the Toolkit. This sadly did not seem to fix anything.

I then checked the error logs, something I should have done immediately (I didn't even know where they were) and noticed that the errors didn't really have anything to do with the Wordpress files, but the folders above. I have this structure: httpdocs/y/yamahaguitars.nl/domain/*Wordpress-files*.

For some reason Plesk messed up the permissions for these folders (y, yamahaguitars.nl and domain) which is why restoring a backup for the specific site did not work at all.
Once I changed everything back the website worked like a charm again.

I feel kind of bad for jumping the gun on this forum post, but am absolutely positive that it would have taken me ages to find this if it wasn't for your help.

Thank you so much!

 

[MarkM]

The copyright at the bottom of your site has a wonky URL.... Just something I noticed.

 

[Mathijs]

The copyright at the bottom of your site has a wonky URL.... Just something I noticed.

Ah nice catch! Just changed it ;-) Thanks!

 

[Brujo]

ok @Mathijs and when you adjust your mixed content (from http -> https like as you can see in your sourcecode http://yourdomain/wp-content/uploads/2013/11/sg-2000-homepage.png) on your website then it going to be good... at the moment Modern browsers display warnings about this type of content to indicate to the user that this page contains insecure resources....

see for explanation: What Is Mixed Content? | Web Fundamentals | Google Developers

@Mark Muyskens - not just fixed we also improved it

 

[Mathijs]

Oh wow you guys are killing it!

Haha thanks a bunch, will definitely fix that as soon as possible.