It would be good to get a bit more information about your setup?
Such as, which version of Umbraco are you using, any details about your hosting setup (e.g. Azure App Service / Windows Server 2016 VPS etc)
Also, are you seeing the 403 error in the umbraco backoffice, or on the front of the website, or both? Does it affect every page, or just specific pages?
403 Forbidden is usually related to permissions or security settings so might pay to check your file and folder permissions are correctly applied on the host.
Just to add an update here - I had a similar issue on the entire v8 website in my Windows hosting package. The support there were not much use and had changed the database connection without letting anyone know - but then we got the 403.14 error.
The site had been working fine before hand and no setting had been changed by us. So I checked the "Enable directory browsing" out of desperation and the site started to work again. I then un-enabled that very same setting and the site continued to work just fine. I had tried recycling the IIS pool and practically anything else I could think of but in the end, it was just a glitch in the system. The site had worked fine on my local too, so it was a painful few days trying to fix a hosting providers screw up.
Why we are getting 403 error
Hi,
Failed to load resource: the server responded with a status of 403 ()
why we are getting this error sometimes but when I reload my page it will be working fine.
Can you please help me out?
Hi Ajay,
It would be good to get a bit more information about your setup?
Such as, which version of Umbraco are you using, any details about your hosting setup (e.g. Azure App Service / Windows Server 2016 VPS etc)
Also, are you seeing the 403 error in the umbraco backoffice, or on the front of the website, or both? Does it affect every page, or just specific pages?
403 Forbidden is usually related to permissions or security settings so might pay to check your file and folder permissions are correctly applied on the host.
Hope this helps, Chris
Just to add an update here - I had a similar issue on the entire v8 website in my Windows hosting package. The support there were not much use and had changed the database connection without letting anyone know - but then we got the 403.14 error.
The site had been working fine before hand and no setting had been changed by us. So I checked the "Enable directory browsing" out of desperation and the site started to work again. I then un-enabled that very same setting and the site continued to work just fine. I had tried recycling the IIS pool and practically anything else I could think of but in the end, it was just a glitch in the system. The site had worked fine on my local too, so it was a painful few days trying to fix a hosting providers screw up.
is working on a reply...