Open VanderDT opened 1 month ago
Heya @VanderDT, Thanks for your report :)
I've found & fixed the issue that's causing this weird error message. However, the issue was in the frontend code, that was about to show another error message that was coming from the server. So yea, fixing the frontend part will hopefully show the "real" error message now.
I've reopened the issue as it's been accidentally closed by the code change. This is not rolled out to the public instances yet. I'll keep this issue updated once it's rolled out.
Does not work (