Cornerstone stopped loading correctly

Cornerstones stopped working. Like if the CSS and JS of the plugin don’t load anymore in the backend.

I currently have this configuration:

WP Core: 5.2.2
X theme: 6.5.6
Cornerstone: 3.5.4

I’ve tried the “usual”: clearing caches, downgrades, upgrades, deactivating classic editor etc. etc., but it still doesn’t work.

Let me know what I should do, please.

Have a nice day

Hello Luca,

Thanks for writing in!

I checked the website and when loading the page in Cornerstone, I see following error message in dev tools Failed to load resource: the server responded with a status of 403 ().

I suggest you to take a look at following thread for solution on the error message:

Let us know how it goes.

Thanks.

Hi.

All file permissions seem ok (folders 755, files 644).

My hosting provider said that it’s not about Mod_Security and sent me his server’s logs:

2019-07-12 09:44:24.376039 [INFO] [38248] [93.67.30.254:61764:HTTP2-463] File not found [/home/eshuadv/public_html/403.shtml]
2019-07-12 09:44:24.815617 [INFO] [38248] [93.67.30.254:61764:HTTP2-505] [ACL] Access to context [/] is denied!
2019-07-12 09:44:24.815644 [INFO] [38248] [93.67.30.254:61764:HTTP2-505] File not found [/home/eshuadv/public_html/403.shtml]
2019-07-12 09:44:24.854487 [INFO] [38248] [93.67.30.254:61764:HTTP2-507] [ACL] Access to context [/] is denied!
2019-07-12 09:44:24.854510 [INFO] [38248] [93.67.30.254:61764:HTTP2-507] File not found [/home/eshuadv/public_html/403.shtml]
2019-07-12 09:44:24.894042 [INFO] [38248] [93.67.30.254:61764:HTTP2-509] [ACL] Access to context [/] is denied!
2019-07-12 09:44:24.894065 [INFO] [38248] [93.67.30.254:61764:HTTP2-509] File not found [/home/eshuadv/public_html/403.shtml]
2019-07-12 09:44:29.209508 [INFO] [38248] [93.67.30.254:61764:HTTP2-531] [ACL] Access to context [/] is denied!
2019-07-12 09:44:29.209547 [INFO] [38248] [93.67.30.254:61764:HTTP2-531] File not found [/home/eshuadv/public_html/403.shtml]
2019-07-12 09:44:34.269510 [INFO] [38248] [93.67.30.254:61764:HTTP2-571] [ACL] Access to context [/] is denied!
2019-07-12 09:44:34.269728 [INFO] [38248] [93.67.30.254:61764:HTTP2-571] File not found [/home/eshuadv/public_html/403.shtml

I’ve also tried to remove and re-create a clean .htaccess, but no luck with that either.

Could you please access the website and tell me what’s wrong?

Hi Luca,

I see that you have a lot of customazation on your child theme, would you mind switching to parent X theme for awhile and see if that resolves the issue.

If that did not resolve the issue, please do testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

Let us know how it goes!

I tried with everything you suggested, but the issue is not solved.

Please tell me if you can take a look at the website with the credentials provided.

If not, tell me where to download X theme 6.1.0 and Cornerstone 3.1.0, because I know those release were stable on my website. I can’t lose anymore time on this and I need to update the content of the website as soon as possible.

Thanks,
Luca

Hey Luca,

Regretfully, we do not have X 6.1.0 available for download anymore. The stable release of X is 6.4.6. You can download it from your Apex Dashboard.

I logged in to your cPanel however, there’s no control in there that could potentially fix the 403 Forbidden issue. This issue can only be resolved by your web host because they have access to all server controls.

Please specifically ask your host why wp-content/plugins/cornerstone/assets/dist/css/app/app.css is forbidden in your site. That will answer why the rest of the CSS is forbidden.

Can you also try asking your host if they can switch your web server to Apache at least temporarily just to test if the type of server is causing the issue.

Please try downgrading to the stable release of X to see if that fixes the issue for now.

Thanks.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.