Commit 04d17561 authored by Dan McArdle's avatar Dan McArdle
Browse files

nixos/vaultwarden: Start after network-online.target 

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/
parent 8331663f

nixos/modules/services/security/vaultwarden/default.nix

+2 −1
Original line number Diff line number Diff line
@@ -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;