• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue 403 errors on .js and .css files on first load, solved on refresh

rupeski

New Pleskian
I am hoping someone can help.

I have an issue with pages on my website returning 403 errors on some .js and .css files and images on the first load - visible in the Chrome inspect console. This causes the page to render improperly. Oddly, all the issues are resolved on a page refresh. If I do a hard refresh, the problems reappear, if I do a normal refresh they are resolved.

I have put hours into this, but I think it may be an issue with the server/IIS/Plesk, since the exact same page served from a different machine has no issues at all.

A test page on the live server (which is administered through Plesk) that shows the errors is here: [redacted] The exact same page served on the test server and showing no errors is here: [redacted]

The actual homepage on which the errors are also visible is [redacted] and the test website showing no errors is [redacted]

To see the issue, open the inspect console and see the 403 errors returned on the scripts that are trying to load. It happens on all browsers.

Both the live machine and the test machine are running Windows/IIS

I would be grateful for any help that can be offered.

Thanks
 
Last edited by a moderator:
Sometimes, this issue can be related to caching settings. Check your server and browser cache settings to ensure they are not causing the 403 errors.
 
Back
Top