-
|
After updating to the latest version, I have constant restarts of the wiredoor container. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 9 replies
-
|
Hi! Thanks for reporting this. The latest release runs services as a non-root user by default, which can surface permission issues that were masked before. To help us debug the constant restarts, could you please share logs or details? |
Beta Was this translation helpful? Give feedback.
-
|
docker compose logs -f |
Beta Was this translation helpful? Give feedback.
-
|
After executing the command docker compose exec -u root wiredoor chown -R 1000:1000 /data `wiredoor | time="2025-09-10T17:26:30+02:00" level=warning msg="process reaping disabled, not pid 1" |
Beta Was this translation helpful? Give feedback.
-
|
It's better now, my applications are working, but I can't connect via https. I get warnings from my browser saying “Not connected: potential security risk.”
|
Beta Was this translation helpful? Give feedback.
-
docker compose exec -u root wiredoor chown -R 1000:1000 /etc/letsencrypt /var/lib/letsencrypt /var/log/letsencrypt |
Beta Was this translation helpful? Give feedback.
-
|
no change
|
Beta Was this translation helpful? Give feedback.
If you don’t want to run the container as non-root, you can force it to run as root by editing your
docker-compose.ymland adding theuserdirective:This way the container will behave the same as in previous releases.
However, we recommend the non-root setup for better security.
Thanks to your feedback I was able to reproduce the issue and I’ve added the proper upgrade steps to the release notes.