• TalkBass has been independent since 1998. Add your voice.
    Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
    Join free Log in
    Want zero display ads or expanded classifieds tools? Compare plans.

Error message: Oops! We ran into some problems. The search could not be completed. Please try again later.

#22
I'm terribly sorry, I had not received any notifications from this thread since the original issue was fixed in Jan 2025. This new issue is not related to the thread title in that it's not about search, correct? Just random 'oops' messages?

To all that are experiencing this issue, are you running a browser extension to block ads or other privacy extensions? I'm just starting to troubleshoot this but AI gives this quick overview:

This error in XenForo usually indicates a JavaScript conflict or security tool blocking cross-origin communication, often manifesting as "Oops! We ran into some problems". It frequently occurs when an iframe (like an editor, ad, or embed) fails to load properly or tries to send data to a different domain/protocol than the main page. [1, 2, 3, 4]
Common Fixes and Troubleshooting:
  • Check Browser Console: Press F12 to open the developer tools and look at the "Console" tab for specific details on what failed.
  • Browser Extensions: Disable ad blockers or privacy extensions (e.g., uBlock, Privacy Badger) which often cause postMessage issues.
Edit: Nevermind the above, I believe I have found the issue. It seems to be Cloudflare blocking 'keep-alive' requests, because from certain IP's it thinks these Ajax requests (commonly called "heartbeat" requests, they basically keep your session active) are coming from automated bots. I'm putting in a firewall rule that should whitelist these requests.
 
Last edited:
  • Like
Reactions: Flying B, Backdrop and BassComa
#24
paul said:
Edit: Nevermind the above, I believe I have found the issue. It seems to be Cloudflare blocking 'keep-alive' requests, because from certain IP's it thinks these Ajax requests (commonly called "heartbeat" requests, they basically keep your session active) are coming from automated bots. I'm putting in a firewall rule that should whitelist these requests.
Click to expand...

Hi Paul,

I have not had any problems since you fixed this so it seems to work! :)
 
  • Like
Reactions: Zooberwerx

Latest posts

Top Bottom
Back