production with Clerk
I have deployed to production, but my url dns is not yet resolving, so I can only access the app at the {app-name}.vercel.app url
the clerk login does not work, when I click the sign in button, nothing happens. Is this expected behavior. I am unclear if Clerk only works on the specified url
in the console, I see this message
69-26fa0db619535114.js:1 Failed to authenticate: "No auth provider found matching the given token", check your server auth config
13 Replies
There are DNS steps to take when going to production with Clerk, have you done that?
Docs here: https://clerk.com/docs/deployments/overview
Deployments & Migrations: Deploy your Clerk app to production
Learn how to deploy your Clerk app to production.
Yes I think everything is set up correctly, but I am still waiting for the DNS change to propagate
You might need to wait for the propagation. Clerk prod setup relies on being served from the same domain.
felt like forever, but its propogated now
still getting an error, must have something still configured wrong
Sign in now seems to work, but than the front end seems to think no one is signed in but clerk says:
"Clerk:
The SignIn or SignUp modals do not render when a user is already signed in, unless the application allows multiple sessions. Since a user is signed in and this application only allows a single session, this is no-op.
Double check https://docs.convex.dev/auth/clerk#configuring-dev-and-prod-instances
And if all else fails: https://docs.convex.dev/auth/debug
Debugging Authentication | Convex Developer Hub
You have followed one of our authentication guides but something is not working.
Convex Clerk | Convex Developer Hub
Clerk is an authentication platform providing login via
checking now, just realized I am still getting this error "No auth provider found matching the given token"
this looks like what it might be https://discord.com/channels/1019350475847499849/1206932126025646110/1206937733826748446
never mind the CLERK_JWT_ISSUER_DOMAIN already covers that
walking through debugging auth now
answer: I see a log with 'server identity' null:
proceeding to step 2
@Michal Srb I think In found the error but still not sure what to do
771-58b9dd19c5f8171c.js:1
GET https://clerk.everwhz.com/npm/@clerk/clerk-js@4/dist/clerk.browser.js net::ERR_NAME_NOT_RESOLVED in the env convex dashboard CLERK_JWT_ISSUER_DOMAIN is set to https://clerk.everwhz.com
GET https://clerk.everwhz.com/npm/@clerk/clerk-js@4/dist/clerk.browser.js net::ERR_NAME_NOT_RESOLVED in the env convex dashboard CLERK_JWT_ISSUER_DOMAIN is set to https://clerk.everwhz.com
this may be the issue https://clerk.com/docs/deployments/overview#dns-records
Deployments & Migrations: Deploy your Clerk app to production
Learn how to deploy your Clerk app to production.
CLERK_JWT_ISSUER_DOMAIN should come from your JWT template, is that the Issuer URL?
In your Clerk prod instance
I got it working the issue is that the url, doesn't exist, until the CNAME records are added for CLERK, there are five CNAME Clerk requires
if you follow this carefully it should work https://clerk.com/docs/deployments/overview#dns-records
Deployments & Migrations: Deploy your Clerk app to production
Learn how to deploy your Clerk app to production.
mine is working, I think for the google part to work, I just have to wait for google to verify it
for clerk follow above, than for google follow https://clerk.com/docs/authentication/social-connections/google
Sign Up & Sign In: Google
Learn how to set up social connection with Google.
not sure when it will work, or what to make of google errors,
Verification in progress
The Trust and Safety team has received your form. They will reach out to you via your contact email if needed. The review process can take up to 4-6 weeks. Expect the first email from our Trust and Safety team within 3-5 days. Your last approved consent screen is still in use. Learn more
Clerk and Convex seem to work together now