Repository navigation
WebUI wont comeup on a synology NAS #324
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
Ive tried this on two different synology NAS units, running DSM 7.2.2.
In both cases, while the container seems to start, the webui wont come up. No indication in the log for anything related.
see attached docker build log
Expected Behavior
No response
Steps To Reproduce
Using the standard docker compose from https://hub.docker.com/r/linuxserver/transmission
Environment
synology nas, DSM 7.2.2
Creating docker using synology's Container managerCPU architecture
x86-64
Docker creation
---
services:
transmission:
image: lscr.io/linuxserver/transmission:latest
container_name: transmission
environment:
- PUID=1026
- PGID=100
- TZ=Etc/UTC
- TRANSMISSION_WEB_HOME= #optional
- USER= #optional
- PASS= #optional
- WHITELIST= #optional
- PEERPORT= #optional
- HOST_WHITELIST= #optional
volumes:
- /volume1/docker/transtest/config:/config
- /volume1/data/Downloads:/downloads #optional
- /volume1/docker/transtest/watch:/watch #optional
ports:
- 9091:9091
- 51413:51413
- 51413:51413/udp
restart: unless-stoppedContainer logs
html file attached
Activity
github-actions commentedon Jun 1, 2026
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Tomsauy commentedon Jun 1, 2026
Same Issue with DSM 6.2.3 and Docker
alirz1 commentedon Jun 1, 2026
i tested and 4.1.0 works fine. But 4.1.1 does not as reported above in my original pose.
thespad commentedon Jun 1, 2026
Can you provide the output of
cat -v /proc/net/if_inet6from both the host and inside the container. I suspect this is some "Synology using EOL kernels" issue again.alirz1 commentedon Jun 2, 2026
they look like:
fe800000000000002c0501fffe4a1c83 3c 40 20 80 docker502327b
fe8000000000000000429cfffeeb4ca1 0d 40 20 80 docker0
thespad commentedon Jun 3, 2026
So there is a functional IPv6 interface but for whatever reason Transmission is failing to start up when bound to it.
alirz1 commentedon Jun 4, 2026
issue exists in transmission 4.1.2 also.
alirz1 commentedon Jun 4, 2026
can i provide something from the synology that will help fix this issue?
alirz1 commentedon Jun 4, 2026
ok. I found out that the following parameter is causing the rpc to ONLY bind to ipv6. This parameter is there by default when the container is built and set as : "rpc-bind-address": "[::]"
Changing that to 0.0.0.0, makes the webui start and work normally.
diskape commentedon Jun 18, 2026
Same on QNAP, webui doesnt work. So not limited to synology.
Stopped working after update on the 16.06.
Error log mentions findings above:
ERR rpc-server.cc:827 Couldn't bind to 0.0.0.0:9091 after 10 attempts, giving up (rpc-server.cc:827)
EDIT: adding version
Linuxserver.io version: 4.1.2-r0-ls349
Build-date: 2026-06-16T15:25:32+00:00
LinuxServer-CI commentedon Jul 18, 2026
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
mksoc commentedon Sep 10, 2026
Same issue here on Synology with DSM 7.4.1 and image version 4.1.3 (also tried with 4.1.0). Any updates? Also, it's probably related to #325
LinuxServer-CI commentedon Oct 10, 2026
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.