Open Hexdump74 opened 3 years ago
Sorry, it was an artifact of my browser. I missed a step during installation, got this error, corrected the installation, but the error stayed in my cache. Opening a new private window bring me to the expected login page.
Finally, no, the error is still showing. It is pretty random, I'm still searching for the reasons.
Looks like the login screen loads without problems on Chromium, but sometimes fails on Firefox.
Thanks for the report @Hexdump74!
This error shows up when the getWorkspace call in Boardpage.tsx fails.
We can keep this issue open for now. Longer term we need to handle invalid sessions better, e.g. log-out and re-login.
Testing more, I noticed that behavior on FireFox is different than Chrome:
Might be something off with the timing on FireFox. As a short-term fix, I filed #274 to add a re-login button to the error page, and should have a fix for that in shortly.
Thanks. So finally it was indeed related to my browser's cache. So I keep the issue open as a reminder ?
Thanks @Hexdump74. On my machine (macOS 10.15.7), I see an issue with FireFox:
I believe this is a timing issue with FireFox, and updated the title to reflect it. More context:
NS_BINDING_ABORTED
error in the FireFox network console when redirecting to /loginIf you (or anyone else) can help verify this behavior on Linux and other platforms, that would be super helpful!
I'm totally unable to reproduce the bug now... I reinstalled the server (because I deleted the VM used for the first test), and now I am always correctly redirected to the login page. If you have a server with which you reproduce the problem and it is accessible from Internet, I could connect on it with my Linux.
I got this when I upgraded from one version to another. Stopping the server, moving focalboard.db out of the folder and then restarting solved the problem. Not sure why.
this happens on the most recent update on a completely clean and updated chrome for me as @ericgaspar mentioned above.
Thanks @brimwats! To confirm: Does clicking on the "Log in again" button on the error page work around the issue?
no. there are gifs at the end of focalboard_ynh/issues/1
Summary: After fresh new installation on ubuntu 18.04, the first page give me an error :
/error?id=no_workspace
The logs contain anAPI ERROR 401, err: no session token
.Steps to reproduce the behavior:
Expected behavior: A login screen to create the first user
Screenshots: An empty grey screen only showing a rectangle where is written "Error". No more text or description. The adress bar links to /error?id=no_workspace
Platform:
Additional context: The databases (i tried with both pgsql and sqlite) contain a table workspace :
Logs extract :