Permission issues with 1.26.0 #1957

New Issue

MrUnknownDE · 2026-04-06T02:45:28+02:00

MrUnknownDE commented

2026-04-06 02:45:28 +02:00

Originally created by @mdrichardson on 10/14/2022

Subject of the issue

Updating to the latest 1.26.0 results in Vaultwarden failing to start properly. This results in a 503 when trying to access through my proxy, and ERR_CONNECTION_REFUSED when accessing via local ip:port.

systemd logs look fine:

Oct 14 18:19:03 vw vaultwarden[391]: [2022-10-14 18:19:03.597][start][INFO] Rocket has launched from http://127.0.0.1:8000

But journalctl logs show some permissions issuse:

Oct 14 18:14:28 vw vaultwarden[108]: [2022-10-14 18:14:28.760][start][INFO] Rocket has launched from http://127.0.0.1:8000
Oct 14 18:14:28 vw systemd-hostnamed[123]: Failed to read product UUID, ignoring: Permission denied
...
Oct 14 18:14:28 vw systemd-networkd[73]: Could not set hostname: Permission denied
Oct 14 18:14:28 vw networkd-dispatcher[102]: No valid path found for iwconfig
Oct 14 18:14:28 vw networkd-dispatcher[102]: No valid path found for iw
...
Oct 14 18:14:28 vw postfix/postfix-script[253]: warning: symlink leaves directory: /etc/postfix/./makedefs.out

Deployment environment

vaultwarden version: 1.26.0

Install method:

I run VW in a Proxmox LXC, using the docker extract method.

Other relevant details:

Typically, I update VW using this script:

wget https://raw.githubusercontent.com/jjlin/docker-image-extract/main/docker-image-extract && \
chmod +x docker-image-extract && \
./docker-image-extract vaultwarden/server:alpine && \
mv output/vaultwarden /opt/vaultwarden && \
service vaultwarden stop && \
cp -rlf output/web-vault /opt/vaultwarden && \
rm -Rf output && \
rm -Rf docker-image-extract && \
service vaultwarden start
echo -e \nMUST REBOOT FOR CHANGES TO TAKE EFFECT\n

Updates have worked in the past, but this is the first to stop working. I also chown'd everything to my vaultwarden user and still ran into this issue.

Steps to reproduce

Update to the latest version from the docker extracted method.

Expected behaviour

VW to start the web server and be able to access it.

Actual behaviour

VW service reports the web server starts fine, but it is inaccessible.

Troubleshooting data

This is my systemd service:

[Unit]
Description=Bitwarden Server (Rust Edition)
Documentation=https://github.com/dani-garcia/vaultwarden
After=network.target

[Service]
User=vaultwarden
Group=vaultwarden
EnvironmentFile=/var/lib/vaultwarden/.env
ExecStart=/opt/vaultwarden/vaultwarden
LimitNOFILE=1048576
LimitNPROC=64
PrivateTmp=true
PrivateDevices=true
ProtectHome=true
ProtectSystem=strict
WorkingDirectory=/var/lib/vaultwarden
ReadWriteDirectories=/var/lib/vaultwarden
AmbientCapabilities=CAP_NET_BIND_SERVICE

[Install]
WantedBy=multi-user.target

*Originally created by @mdrichardson on 10/14/2022* ### Subject of the issue Updating to the latest 1.26.0 results in Vaultwarden failing to start properly. This results in a 503 when trying to access through my proxy, and ERR_CONNECTION_REFUSED when accessing via local ip:port. systemd logs look fine: ``` Oct 14 18:19:03 vw vaultwarden[391]: [2022-10-14 18:19:03.597][start][INFO] Rocket has launched from http://127.0.0.1:8000 ``` But journalctl logs show some permissions issuse: ``` Oct 14 18:14:28 vw vaultwarden[108]: [2022-10-14 18:14:28.760][start][INFO] Rocket has launched from http://127.0.0.1:8000 Oct 14 18:14:28 vw systemd-hostnamed[123]: Failed to read product UUID, ignoring: Permission denied ... Oct 14 18:14:28 vw systemd-networkd[73]: Could not set hostname: Permission denied Oct 14 18:14:28 vw networkd-dispatcher[102]: No valid path found for iwconfig Oct 14 18:14:28 vw networkd-dispatcher[102]: No valid path found for iw ... Oct 14 18:14:28 vw postfix/postfix-script[253]: warning: symlink leaves directory: /etc/postfix/./makedefs.out ``` ### Deployment environment * vaultwarden version: 1.26.0  * Install method: I run VW in a Proxmox LXC, using the [docker extract method](https://github.com/dani-garcia/vaultwarden/wiki/Pre-built-binaries#extracting-binaries-without-docker-installed). * Other relevant details: Typically, I update VW using this script: ```bash wget https://raw.githubusercontent.com/jjlin/docker-image-extract/main/docker-image-extract && \ chmod +x docker-image-extract && \ ./docker-image-extract vaultwarden/server:alpine && \ mv output/vaultwarden /opt/vaultwarden && \ service vaultwarden stop && \ cp -rlf output/web-vault /opt/vaultwarden && \ rm -Rf output && \ rm -Rf docker-image-extract && \ service vaultwarden start echo -e \nMUST REBOOT FOR CHANGES TO TAKE EFFECT\n ``` Updates have worked in the past, but this is the first to stop working. I also `chown`'d everything to my vaultwarden user and still ran into this issue. ### Steps to reproduce Update to the latest version from the docker extracted method. ### Expected behaviour VW to start the web server and be able to access it. ### Actual behaviour VW service reports the web server starts fine, but it is inaccessible. ### Troubleshooting data This is my systemd service: ``` [Unit] Description=Bitwarden Server (Rust Edition) Documentation=https://github.com/dani-garcia/vaultwarden After=network.target [Service] User=vaultwarden Group=vaultwarden EnvironmentFile=/var/lib/vaultwarden/.env ExecStart=/opt/vaultwarden/vaultwarden LimitNOFILE=1048576 LimitNPROC=64 PrivateTmp=true PrivateDevices=true ProtectHome=true ProtectSystem=strict WorkingDirectory=/var/lib/vaultwarden ReadWriteDirectories=/var/lib/vaultwarden AmbientCapabilities=CAP_NET_BIND_SERVICE [Install] WantedBy=multi-user.target ```

MrUnknownDE closed this issue

2026-04-06 02:45:28 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1957