Not authenticated after successful sign in request
i dont know the reason for this but sometimes i have a problem that after page reload two problems happen
1. while user having JWT token set auth returns authenticated = false and loading = false. my app tries to sign in because of this
2. sign is successful like you see in the debug log. but auth is not set to true.
this happens from time to time but not always. reloading page again fixes it and JWT token is used again

6 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
i found how i can reproduct this error. i enabled vpn and loaded page. than disabled vpn and loaded it again and than this happens. tested multiple times. but doesnt happen always
so seems the problem happens when network changes. i think similar happened when switched between wifi and cellular


Could you file on issue on convex-auth GitHub repo? Sounds like it might have to do with the websocket reconnecting over different networks?
ok