Answered by
junkaiman
Oct 29, 2025
Replies: 3 comments
|
Can you please check the logs of the Tinyauth container? Since the authentication requests don't happen in the browser, CORS does not apply, what you are seeing is probably some other errors not related to Tinyauth. |
0 replies
0 replies
|
I think I figured this out. Posting this here in case someone else encountered the same scenario. In order to make it work for domain B.com, you will need to create another Tinyauth service under that domain. So I kept the following setup: And also
Correct me if I'm wrong! |
0 replies
Answer selected by
junkaiman
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


I think I figured this out. Posting this here in case someone else encountered the same scenario.
In order to make it work for domain B.com, you will need to create another Tinyauth service under that domain. So I kept the following setup:
Pocket ID: auth.A.comTinyauth for A.com: tinyauth.A.comTinyauth for B.com: tinyauth.B.comApp1: whoami.A.comApp2: whoami.B.comAnd also
https://tinyauth.A.com/api/oauth/callback/pocketidandhttps://tinyauth.B.com/api/oauth/callback/pocketidas callback URLstinyauth-A,tinyauth-Bto Traefik configsApp1totinyauth-Amiddleware and routeApp2totinyauth-BmiddlewareCor…