Applicable to:
- Plesk Onyx for Linux
Symptoms
-
WordPress admin dashboard is not displaying properly: layout is broken. css/js scripts are not loaded.
-
The following or similar error messages are shown in
/var/www/vhosts/example.com/logs/proxy_error_log:CONFIG_TEXT: [error] 1938949#0: *7483 access forbidden by rule, client: 203.0.113.2, server: example.com, request: "GET /wp-admin/load-scripts.php?c=0&load%5B%5D=jquery-core,jquery-migrate,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-resizable,jquery-ui-draggable,jquery-ui-but&load%5B%5D=ton,jquery-ui-position,jquery-ui-dialog,utils,moxiejs,plupload&ver=4.9.6 HTTP/2.0", host: "example.com", referrer: "https://example.com/wp-admin/update-core.php"
-
Browser DevTools (F12 in Google Chrome) > Network tab shows that
load-styles.phpfile cannot be proceeded by a browser due to 403 error (Forbidden response).
Cause
Security settings in WordPress Toolkit.
Resolution
-
Go to Domains > example.com > WordPress > select affected WordPress instance > Security Status (Check Security in older WordPress Toolkit versions).
-
Select Disable scripts concatenation for WordPress admin panel and click Secure.
-
Connect to the server via SSH.
-
Open a file
/var/www/vhosts/example.com/httpdocs/wp-config.phpwith a text editor. -
Add the following record at the end of the file before the
require_oncedirective:CONFIG_TEXT: define('CONCATENATE_SCRIPTS', false);
-
Go to site's document root in Domains > example.com > File Manager:
-
Add the following record at the end of the file before the
require_oncedirective:CONFIG_TEXT: define('CONCATENATE_SCRIPTS', false);
Comments
4 comments
If this is already at the beginning of the file, is this still recommended?
Would we add this anyway leaving them both in place, remove the one from the beginning of the file in addition to adding this to the end, or leave it as-is without adding it at all?
Hello @Greg P,
One is sufficient, no need to add the record twice.
It is showing for all the websites on the server. How to fix over 200 websites ??
Hello @Salman,
Am I correct that you have the same issue for all of these websites?
Have you tried the above steps for some of the websites?
For this particular issue, the solution doesn't look scalable.
In case the issue is different, please, create a request to Plesk Support to have a closer look at the issue.
Please sign in to leave a comment.