Admin throwing fatal error

[gabek]

Admin throwing fatal error

[mahmed2000]

That modal with that message explicitly checks if the server status context has an error, and is of error type OWNCAST_SERVICE_UNREACHABLE (string, === match). That is only ever set if the repeating /status api calls result is an instanceof Error.

Nothing stands out that would cause that on the frontend. If you tested this locally, then I imagine this would be a backend issue instead. The logs say anything? Is this only on my bcrypt branch or does this happen generally on develop currently?

[gabek]

I didn't dig too deep into it, but I did also test on develop to see if it had anything to do with the hashed password branch, and I did experience it on develop as well. However, if I test on nightly I'm not able to reproduce it, and that is updated with develop every night. There were no visible server-side issues, and there were no failed API calls in the browser when looking client side. I'm guessing it's something small, I'll track it down.

[gabek]

When switching browsers, I was no longer able to reproduce this, so it might be something cached in a single browser on my side.

[mahmed2000]

If you haven't wiped the cache yet, does the network log show the status api call as an error? Transferred in bytes or cached by the service worker?

[gabek]

Nope, there were no client-side errors in the browser. I saw nothing to explain it. The only thing wrong was the text field warning, and that wasn't within the browser.