A note for Unraid Vaultwarden users using swag

This is just a PSA for others that might run into this issue. After months of stable service, I ran into issues with Bitwarden clients unable to log in again if they were fully logged out with a classic “Failure to Fetch” error. After chasing down more complex solutions, it turned out that my swag proxy network on Unraid had renumbered itself and the vaultwarden container had a new ip. Quick update in the swag config all everything was sunny again (for some reason I could never get container name resolution to work, which I know is preferred).

So, always good to check the simple stuff first…