-
Hey guys, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
Looks like the token verification is failing, or that the token is modified at the receivers end by the mail client or something. What do the logs say during the time the user clicked this links and tried to register or verify? |
Beta Was this translation helpful? Give feedback.
-
I saw that in the logs as well but nothing I try seems to fix it. this is the log for verify. [2021-11-04 19:39:00.367][vaultwarden::api::identity][ERROR] Please verify your email before trying again.. IP: 192.168.1.1. Username: dtest@thescholarsloft.org. [2021-11-04 19:39:00.367][response][INFO] POST /identity/connect/token (login) => 400 Bad Request Here is the invite [2021-11-07 07:35:51.470][response][INFO] POST /api/accounts/register (register) => 400 Bad Request |
Beta Was this translation helpful? Give feedback.
-
OK guys so I don't know if anyone will ever have this issue. I an using ngnix proxy manager for my reverse proxy. When I go to bitwarden.mydomain.com it redirects me to bitwarden.mydomain.com/#/ so when I went into my vaultwarden admin console to enter the Domain URL I naturally copied it from the browser and pasted it in the field. Apparently the /#/ caused vaultwarden to send a join link with https://bitwarden.mydoman.com/#//%23/accept-organization/ which caused nginx to redirect me to the "correct" page stripping the token from the url and sending me to the main page. After changing the domain URL to bitwarden.mydomain.com the invite was sent in the correct format https://bitwarden.mydoman.com/#/accept-organization/. Bottom line Is to make sure that your domain URL is correct and don't add the /#/ because it will cause major issues. @BlackDex Thank you for pointing me in the right direction. Your time and patience is appreciated. If there was something that I didn't explain correctly please correct me. |
Beta Was this translation helpful? Give feedback.
OK guys so I don't know if anyone will ever have this issue. I an using ngnix proxy manager for my reverse proxy. When I go to bitwarden.mydomain.com it redirects me to bitwarden.mydomain.com/#/ so when I went into my vaultwarden admin console to enter the Domain URL I naturally copied it from the browser and pasted it in the field. Apparently the /#/ caused vaultwarden to send a join link with https://bitwarden.mydoman.com/#//%23/accept-organization/ which caused nginx to redirect me to the "correct" page stripping the token from the url and sending me to the main page. After changing the domain URL to bitwarden.mydomain.com the invite was sent in the correct format https://bitwarden.myd…