Closed leandrorius closed 5 months ago
Hm, thanks for reporting this. Can you try adding
VECTR_EXTERNAL_HOSTNAME=
To your .env file with the same setting as VECTR_HOSTNAME and see if that resolves the issue?
@SRAPSpencer Your suggestion worked perfectly! I've just added VECTR_EXTERNAL_HOSTNAME=vectr.mycompany.com to .env file (keeping VECTR_HOSTNAME as well), restarted docker, and the problem is solved.
Awsome, thank you!
Describe the bug Using a VECTR instance with a internal DNS entry (ex: vectr.mycompany.com) causes errors while trying to login with an invalid user or passorwd, or login with MFA enabled, or first-time access password changes. Everything works fine until the submit of user and password. After the submit on any of the situations mentioned, the user is redirected from vectr.mycompany.com to sravectr.internal, causing a name resolution failure. When accessing with a valid user, valid password and no MFA enabled, this error does not happens. The user is redirected to the VECTR main page correctly.
Here's the .env used:
To Reproduce Steps to reproduce the behavior:
Expected behavior The user should stay on vectr.mycompany.com and receive a "invalid username or password" error instead of being redirected to sravectr.internal
Additional context When I add sravectr.internal to my hosts file pointing to the VECTR server IP, the problem is workarounded.