When serving Vaultwarden under a custom port like the Home Assistant add-on does, it's currently impossible to configure Goldwarden correctly via its GUI or goldwarden config set-server:
$ goldwarden config set-server https://example.com:7277
Done
$ goldwarden config get-environment
{"api":"https://example.com/api","identity":"https://example.com/identity","notifications":"https://example.com/notifications","vault":"https://example.com"}
One can work around this by setting all URLs individually:
$ goldwarden config set-vault-url https://example.com:7277
Done
$ goldwarden config set-api-url https://example.com:7277/api
Done
$ goldwarden config set-identity-url https://example.com:7277/identity
Done
$ goldwarden config set-notifications-url https://example.com:7277/notifications
Done
$ goldwarden config get-environment
{"api":"https://example.com:7277/api","identity":"https://example.com:7277/identity","notifications":"https://example.com:7277/notifications","vault":"https://example.com:7277"}
When serving Vaultwarden under a custom port like the Home Assistant add-on does, it's currently impossible to configure Goldwarden correctly via its GUI or
goldwarden config set-server:$ goldwarden config set-server https://example.com:7277 Done $ goldwarden config get-environment {"api":"https://example.com/api","identity":"https://example.com/identity","notifications":"https://example.com/notifications","vault":"https://example.com"}One can work around this by setting all URLs individually:
$ goldwarden config set-vault-url https://example.com:7277 Done $ goldwarden config set-api-url https://example.com:7277/api Done $ goldwarden config set-identity-url https://example.com:7277/identity Done $ goldwarden config set-notifications-url https://example.com:7277/notifications Done $ goldwarden config get-environment {"api":"https://example.com:7277/api","identity":"https://example.com:7277/identity","notifications":"https://example.com:7277/notifications","vault":"https://example.com:7277"}