XF 2.2 Oops! We ran into some problems – 403 error

[Hotfix]

When I try to save the code I get the following message:

Oops! We ran into some problems.

I've checked the browser console and it's a 403 error.



I read the amazing instructions @Brogan gave to us who are dealing with this error message:

XF 2.2 - Oops! We ran into some problems. Please try again later. More error details may be in the browser console.

This comes up time and time again so a sticky thread is in order. If you encounter this error message and you are using a computer (rather than a mobile device), access the browser console (F12 if using Windows / Chrome). Select the Console tab and there should be an error message displayed...

xenforo.com

So I did what the thread suggested me to do – I contacted my webhost (Namecheap) and got them to try to solve the problem.

But the error message still persists, and Namecheap.has told me that there's not more they can do to try to fix the situation.

I don't believe that ModSecurity, mod_evasive, or similar, is the cause of 403 error in my case.


What are your suggestions?

 

[Ozzy47]

If it’s a 403 then it’s server side. Screenshot of the error in the console?

 

[Hotfix]

If it’s a 403 then it’s server side. Screenshot of the error in the console?

Sure. Did I post the right thing?

 

[Paul B]

There's nothing that can be done from within XF to resolve server side errors, which is what a 403 error is.

 

[Hotfix]

There's nothing that can be done from within XF to resolve server side errors, which is what a 403 error is.

This is the response I got from Namecheap:

I am deeply sorry that the investigation took much time. I'm afraid that this case requires attention of a web-development specialist. Unfortunately, as we are not a web-development company, we cannot provide such a service. Thus, I would suggest contacting a web-developer keen in situations of this kind to proceed with the investigation.

 

[Paul B]

That's ludicrous.

Tell them to escalate the ticket to the next level of support, or find a new host.

 

[Hotfix]

That's ludicrous.

Tell them to escalate the ticket to the next level of support, or find a new host.

This is the response I got when I contacted them the day after:

We have checked the issue with our technicians. Unfortunately, the issue is not related to the operation of the server. Please contact a website developer to resolve the issue.

 

[Hotfix]

The problem (403 error) has been resolved after they whitelisted my IP address.

 

[Ozzy47]

I’d find a new host, they are obviously not capable.

 

[Paul B]

Good to hear that it's resolved but they clearly need to educate their first (and second?) level support staff a bit better.

 

[Capital Cichlid]

I am having the same issue on Namecheap. Does this mean they need to whitelist all of website backend user's IP addresses? That is not very convenient.

 

[Allec888]

If someone has this problem, go to your cPanel and deactivate your ModSecurity, after finishing your modifications, just activate it.

 

[TPerry]

Really, if you have this issue you need to make sure that your hosting provider has updated to the latest ModSecurity definitions... they released a wonky one a few weeks ago and this happened to a LOT of XF sites.