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

[Reallybigidea.com]

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

 

[Paul]

Do you remember what you were doing when you encountered this error?

 

[Reallybigidea.com]

Do you remember what you were doing when you encountered this error?

I tryed to send a message via pm.

 

[Paul]

We don’t have a corresponding entry in our error log. Do you have more information that may help us troubleshoot the issue?

 

[internext]

Do you have more information that may help us troubleshoot the issue?

https://xenforo.com/community/threads/oops-we-ran-into-some-problems-–-403-error.192841/

 

[Paul]

https://xenforo.com/community/threads/oops-we-ran-into-some-problems-–-403-error.192841/

Thanks, but that's just XenForo's generic error message--it can be caused by just about anything. The underlying cause in that thread was ModSecurity + cPanel, but NamePros doesn't use ModSecurity (or cPanel, or Apache).

Unlike vanilla XenForo, NamePros logs most user-facing errors, even if they're expected. For example, if you try to post a thread but receive an error message indicating that you're not allowed to post links, we log that. If you subsequently contact support, the tech team can pull up those error messages along with technical details that could help identify any problems on our end.

In this case, no relevant error messages were logged, which is concerning. Any additional information about the incident would be helpful. For example, did the message eventually go through on a subsequent attempt? Was there something in the message that might've looked like spam to our system?

NamePros is relatively big for a PHP-based website, especially one running XenForo--certainly not the biggest, but big enough that we're often navigating uncharted territory. It's not unusual for us to encounter all manner of obscure bugs. Our dev team is no stranger to debugging these, but the first step is always getting as much context as we can.

 

[internext]

Thanks for the reply @Paul. I should have known that seemed too easy. Best wishes

 

[Paul]

I found the cause. You were receiving an error instructing you to disable your VPN, but the error response was formatted for XenForo 1, not XenForo 2. I've written a fix that should be deployed in about five minutes. You'll still receive the same error message when your VPN is enabled, but it'll be a specific error instead of the generic one you were seeing.