Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to check token error #1053

Open
rmayergfx opened this issue Jan 9, 2025 · 3 comments
Open

Failed to check token error #1053

rmayergfx opened this issue Jan 9, 2025 · 3 comments
Labels
type:bug Something isn't working
Milestone

Comments

@rmayergfx
Copy link

ERRO[2025-01-09T14:34:06Z] Failed to check token error="error parsing token: error parsing token: token is malformed: token contains an invalid number of segments"

v1.7.4 installed in docker.

Error is seen when i try to access via web-extension or after reboot.

how to fix this?

@rmayergfx rmayergfx added the type:bug Something isn't working label Jan 9, 2025
@github-project-automation github-project-automation bot moved this to To do in Roadmap Jan 9, 2025
@Oxyaxion
Copy link

Hello same for me on freebsd just after an upgrade from the git repo from the latest v1.7.4

time="2025-01-10T20:30:49+01:00" level=warning msg="x.x.x.x- shiori [10/Jan/2025:20:30:49 +0100] \"GET /api/v1/auth/me\" 403 27 \"https://domain.fr/\" \"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36\" (1ms)" clientIP=x.x.x.x dataLength=27 hostname=shiori latency=1 method=GET path=/api/v1/auth/me referer0

Authentication never finish ... When I press CTRL + F5 I can login in kind of "read only mode", I can read my url but can't add it anymore.

@fmartingr
Copy link
Member

Can you provide more details about your setup, as the issue template suggests? I have been running 1.7.4 before release (I test releases manually) and I haven't experienced any of this. What browser are you using? What do you see in the browsers console?

@fmartingr fmartingr added this to the 1.7.5 milestone Jan 10, 2025
@Oxyaxion
Copy link

Everything works fine after a whole reboot of the plateform ... probably yet another nginx/reverse-proxy/ browser cache issue ... Sorry for the noise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
Status: To do
Development

No branches or pull requests

3 participants