IsmailK
IsmailK
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
I will close this, since I am switching to supabase.
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
I just couldnt find in the docs how to update the authentication configuration
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
I set up a new project in convex and clerk. This time I did not push anything to production on convex or clerk and I still get the same error. Which makes no sense. Again there is no authentication configuration in convex dev dashboard.
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
Right now the values in the authentication configuration of the convex prod are what should be in the convex dev. And in the convex dev there is no authentication configuration. Do I just delete the project and start over?
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
I just need to know how to correct the authentication variables in the prod en dev environement of convex
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
In the convex production the jwt issuer of clerk is the production jwt issuer , but in the authentication section the domain is the clerk dev env jwt issuer. That confuses me. How do I fix that?
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
I think I know what is wrong. I pushed the convex to production with clerks dev env variables as well yesterday night. I will fix that first.
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
I have also set the JWT issuer properly in the environement variables of convex. So I am not sure what could cause that error.
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
No description
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
sure one second
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
It seems it connects and then disconnects
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
No description
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
I removed the inner ConvexReactClient, but the issue is still there. So I checked the network tab in the browser. And saw the following:
28 replies
CCConvex Community
Created by IsmailK on 3/8/2024 in #support-community
Failed to authenticate No auth provider found matching the given token, check your server auth con
I did go through the docs and read that part, but didnt realize the duplicate ConvexReactClient caused the issues. I will try your solution.... in the morning.
28 replies