There seems to be something wrong with the server overload detection. When I type something into the search bar, it'll take me to the results page just fine, then about 70% of the time when I click on a series from the results it brings me to a page that declares:

"Something went wrong!", and then a text button that says "Try Again".

If I click on Try Again, either it just throws me back to the same error page or resolves and sends me to the series page. Then if I try to edit something on that series page, about 40% of the time I'll get the same error.

I opened the Firefox dev tools menu and it shows two specific errors coming up when this happens:

Too many calls to Location or History APIs within a short timeframe.

This pops up twice, with the associated codes sandbox eval code:1:9 and 1517-ef167af23ebaf0fa.js:1:16340

and

DOMException: The operation is insecure.

Which shows up once, with the code 1517-ef167af23ebaf0fa.js:1:120772

I'm pretty sure this only started happening this week. At first I thought my cover preview script was causing problems but I turned it off and it's still happening. I haven't changed my behaviour in using the site at all and am pretty sure I'm not generating enough requests for this to be happening so often.

Firefox 134.0.2, Windows 11

For visibility I want to say I have been getting the same error message when I click on search results (not advanced searches but directly searching for specific titles by name).

Firefox

Don't expect proper grammar from me. I am not being paid here, so you get internal monologue in written form.

I haven't changed anything in weeks. A new browser update?

I am running firefox v.134.0 if that helps

Don't expect proper grammar from me. I am not being paid here, so you get internal monologue in written form.

As of today, this is still happening. Someone else pointed this out in the general bugs thread as well, but opening a search result in a new tab seems to circumvent the error.

I apologize for the delay. Unfortunately the timing of this particular error is not good as I don't currently have the bandwidth to resolve it. It is at the top of my list though.

No worries, just wanted to check in again since the last response was inconclusive. Glad to hear it's being looked into, thanks.

Not sure if you changed anything but I am no longer having issues

Don't expect proper grammar from me. I am not being paid here, so you get internal monologue in written form.

I wasn't running into this problem for a while but it just started happening again today. If it's still being worked on no problem, just updating.

This is still happening, but with slightly different behaviour. The error page now says:

Application error: a client-side exception has occurred while loading www.mangaupdates.com (see the browser console for more information).

When checking the console it's still throwing the same two errors I mentioned before.

I assume this is still being worked on given that the error page has changed? Also opening a search result in a new tab still seems to work in terms of avoiding the error.

Yes I'm looking into it now. I have no updates.