gador/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

nixos/vaultwarden: Start after network-online.target

Browse Source 
On my system, Vaultwarden fails on boot with an AddrNotAvailable error,
presumably because `services.vaultwarden.config.ROCKET_ADDRESS` is not
available yet.

Here's an example of the startup error in journalctl:

```
Jul 26 21:56:48 banana vaultwarden[2514]: Error: Rocket.
Jul 26 21:56:48 banana vaultwarden[2514]: [CAUSE] Bind(
Jul 26 21:56:48 banana vaultwarden[2514]:     Os {
Jul 26 21:56:48 banana vaultwarden[2514]:         code: 99,
Jul 26 21:56:48 banana vaultwarden[2514]:         kind: AddrNotAvailable,
Jul 26 21:56:48 banana vaultwarden[2514]:         message: "Cannot assign requested address",
Jul 26 21:56:48 banana vaultwarden[2514]:     },
Jul 26 21:56:48 banana vaultwarden[2514]: )
```

According to systemd docs [1], `network.target` has little meaning
during startup, but `network-online.target` actually waits until an IP
address is available. The docs recommend putting `network-online.target`
in both `After=` and `Wants=`.

[1]: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
This commit is contained in:
Dan McArdle
2025-07-27 17:31:09 -04:00
parent 8331663fa9
commit 04d1756118
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
nixos/modules/services/security/vaultwarden/default.nix
View File

@@ -224,7 +224,8 @@ in
users.groups.vaultwarden = { };
systemd.services.vaultwarden = {
after = [ "network.target" ];
after = [ "network-online.target" ];
wants = [ "network-online.target" ];
path = with pkgs; [ openssl ];
serviceConfig = {
User = user;