mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 17:55:58 +03:00
[GH-ISSUE #6322] SSO fails in IPv6-only environments #2403
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2403
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @devksingh4 on GitHub (Sep 23, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6322
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, SHOW_PASSWORD_HINT, ADMIN_TOKEN, IP_HEADER, SSO_ENABLED, SSO_ONLY, SSO_SIGNUPS_MATCH_EMAIL, SSO_CLIENT_ID, SSO_CLIENT_SECRET, SSO_AUTHORITY, SSO_SCOPES, SMTP_HOST, SMTP_SECURITY, SMTP_PORT, SMTP_FROM, SMTP_FROM_NAME, SMTP_USERNAME, SMTP_PASSWORD
Config:
Vaultwarden Build Version
v1.34.3-a2ad1dc7
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Caddy 2.1
Host/Server Operating System
Linux
Operating System Version
Ubuntu 24.04
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Expected Result
The sign on should succeed and present me with the unlock screen.
Actual Result
The SSO hangs forever.
Logs
Screenshots or Videos
Additional Context
I am using Entra ID for SSO. I have validated that other docker containers on that host are able to use IPv6. login.microsoftonline.com supports IPv6 as well.
@devksingh4 commented on GitHub (Sep 23, 2025):
This could be related to #6301 ? I don't see any DNS logs in the docker compose logs though.
@BlackDex commented on GitHub (Sep 23, 2025):
Same for you then. Do you use a DNS64/NAT64 solution?
Because only resolving IPv6 addresses first will then still cause issues with IPv4 only domains.
@devksingh4 commented on GitHub (Sep 23, 2025):
I am running on AWS which I believe has native IPv6, so no DNS64/NAT64.
login.microsoftonline.com natively supports IPv6 per dig output.
@devksingh4 commented on GitHub (Sep 23, 2025):
Rather, it looks like I gave you all useless debug info :)
It looks like there is no internet at all in an IPv6-only environment - I just noticed it when logging in with SSO:
@devksingh4 commented on GitHub (Sep 23, 2025):
Configuration issue on my part 🤦
For future users, you must enable IPv6 in both the docker daemon and the docker compose file. In compose add:
and assign both your reverse proxy container and the bitwarden to that network.
The admin page will say no internet access, probably as it uses an IPv4-only domain to check.