Vaultwarden clients after upgrading to StartOS 0.4 – old .local URL no longer works

StartOS Support
1

Hi everyone,

I wanted to share a small issue I encountered after upgrading to StartOS 0.4, as it may save other Vaultwarden users some troubleshooting time.

My Bitwarden client had previously been configured to connect to Vaultwarden using the old, long service-specific .local URL.

After the upgrade, the Bitwarden client could no longer connect and only returned:

Failed to fetch

Vaultwarden itself was running normally, and the StartOS server was reachable. The cause turned out to be the server URL stored in the Bitwarden client.

With StartOS 0.4, the previous long service-specific .local address is no longer used. The Vaultwarden Web Vault is now exposed through the server hostname plus its assigned port, for example:

https://<startos-hostname>.local:<port>

After checking Vaultwarden → Interfaces → Web Vault, the currently valid local URL could be identified.

This is particularly relevant because logging out of a Bitwarden client removes the ability to simply unlock the previously cached vault offline. A subsequent login requires the Vaultwarden server to be reachable at the configured server URL.

So, for anyone upgrading an existing Vaultwarden installation to StartOS 0.4, it may be worth checking the server URL configured in all Bitwarden clients and comparing it with the current Web Vault URL shown under Interfaces.

Perhaps this could also be mentioned explicitly in the upgrade documentation or migration notes for Vaultwarden users.

Thanks again to the Start9 team for all the work on 0.4.

[Created with the help of ChatGPT, finetuned by me :upside_down_face: .]

2

Hi @degard! Thanks for the feedback and yes this is correct. The invalidation of the .local addresses are not specific to Vaultwarden. Any clients that access any services on your server over the LAN need to be adjusted, to have them pointed at the server-name.local:port# address. If you intend to access remotely over a VPN, it would be your server’s localIP:port. The proper port number can be found under each service’s Interface tab.