-
-
Notifications
You must be signed in to change notification settings - Fork 11.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] next_auth throwing error, if I set AUTH_CASDOOR_ISSUER to anything other then http://localhost:${CASDOOR_PORT}' #5550
Comments
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
Hey there, @rukh-debug! I'm here to help you with any bugs, questions, or contributions. Let's dive in and tackle this issue together! The issue you're experiencing with setting To resolve this issue when using a custom domain or IP, ensure that:
If these configurations are correct and the issue persists, it might be helpful to check the logs for any network-related errors or misconfigurations. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
YEP |
This issue is closed, If you have any questions, you can comment and reply. |
📦 Environment
Docker
📌 Version
latest
💻 Operating System
Other Linux
🌐 Browser
Firefox
🐛 Bug Description
If I set custom domain or Ip as my casdoor url, next_auth have some sort of issue.
Error Log
docker-compose.yml
.env
casdoor application config
What option do not work
- 'AUTH_CASDOOR_ISSUER=https://accounts.${DOMAIN}/'
&&- 'AUTH_CASDOOR_ISSUER=http://100.121.230.45:${CASDOOR_PORT}'
What works
'AUTH_CASDOOR_ISSUER=http://localhost:${CASDOOR_PORT}'
📷 Recurrence Steps
setting AUTH_CASDOOR_ISSUER with anything other then http://localhost:${CASDOOR_PORT}'`
🚦 Expected Behavior
I am expecting so see a login form like this.
proof of its woking as expected (going to login screen) while using localhost
📝 Additional Information
The text was updated successfully, but these errors were encountered: