Open briped opened 1 month ago
I've seen this before in my own implementations - the fix is typically to sign out of Trilium as you mentioned. You also may want to evaluate if there is cache between the browser that's having the issues and the TriliumNext container. Traefik might be using cache in your implementation. If you do have cache enabled, perhaps disabling it will help.
Also, refreshing the page without cache (ctrl + shift + r
) after logging in might help?
TriliumNext Version
0.90.4
What operating system are you using?
Other Linux
What is your setup?
Local + server sync
Operating System Version
Debian GNU/Linux 12 (bookworm)
Description
Accessing Trillium Notes after an indeterminate amount of time (over 1 day?), access fails with the error title :: message "403 POST tree/load :: Invalid CSRF token".
In troubleshooting I have found that opening another browser it works fine, but still fails in the main browser. Even using the Desktop Trillium app works, but I have seen it failing in previous sessions. My best bet for this is the fact that the previous session have not been stored in working clients/browsers.
Looking at the available cookies for the failing and working browsers, the failing shows 2-4
_csrf
tokens, where the working just shows the expected 1_csrf
token.Clearing the cookies in the failing browser resolves the issue, but it returns as described above.
Same issue as this one: https://github.com/zadam/trilium/issues/4186 (my comment)
Client details:
OS:
Browser:
https://brave.com/latest/#desktop-release-notes-v170126
Server details:
OS:
Debian GNU/Linux 12 (bookworm)
Trillium Web App:
compose.yaml
Error logs
Backend logs:
Frontend logs: