Replies: 1 comment
-
|
Specifically, in emdash, there's a wrangler.toml with vars like AUTH_ORIGIN or something. Need to set it to custom domain. Then re-register passkey. If using Cloudflare Access? We'll say: I ran into this same thing last year when moving a worker from *.workers.dev to a custom domain; the passkey is bound to the origin, so you must either update the allowed origins in the auth config or delete and recreate the passkey after deploying to the new domain. Provide steps: 1) In your worker code, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've deployed emdash on cloudflare workers, and with default workers domain I added initial passkey. I saved passkey in Bitwarden.
And, after I added custom domain - and there's no way to sign-in on new domain.
(I deployed with this link - https://deploy.workers.cloudflare.com/?url=https://github.com/emdash-cms/templates/tree/main/blog-cloudflare)
Beta Was this translation helpful? Give feedback.
All reactions