Docker-transmission-openvpn: 404 not found when loading up with transmission-web-control

[ghost]

Here's what loads up

[haugene]

Probably relates to @h45rd's comment on #459 about symlinking index.html?

[ghost]

Permissions error maybe?

Visiting http://ip:9092/transmission/web/tr-web-control/style/base.css (and all other urls) lead to:

404: Not Found
/opt/transmission-ui/transmission-web-control/tr-web-control/style/base.css (Permission denied)

[ghost]

@davinkevin any ideas?

[davinkevin]

Not for the moment... I've proposed a simple (maybe too simple) installation process of the web-ui.
I currently have no time to investigate, but we can find the install process proposed by the dev of the UI

https://github.com/ronggang/transmission-web-control/blob/master/release/install-tr-control.sh

[ghost]

I managed to get the UI working, it definitely was a permissions error where the folder and all the contents of /opt/transmission-ui/transmission-web-control were set to chmod 666, rather then the chmod 755 like the other web UIs.

[ghost]

Maybe to do with the Dockerfile, when creating the folder on this line
https://github.com/haugene/docker-transmission-openvpn/blob/3a10ad860c232ee624b463ee55f48337c18ac120/Dockerfile#L21
causing the folder to have different permissions than the other WebUIs

[haugene]

I took a look at this. It could be a permissions issue, but I can't seem to reproduce it. All commands in Dockerfile is run as root, and when I look at directory ownership of /opt/transmission-ui/ they all are owned by root.

I've tried running transmission as root and my own user, the latest tag and a local build. But I don't get the 404s. We could do chmod 755 for the files in transmission-ui, but are more people having an issue with this?

[mrjackyliang]

I tried this, and everything seems to be working normally. It could possibly be a cached thing.

[ghost]

@coolboiime I think you're right, tried again and it loads perfectly on both Chrome and Firefox. I'll close the issue!

[mnkhouri]

Edit: disregard this comment -- the issue seems fixed in the 2.1 tag. The comment below applies to the 2.0 tag

---

I ran into this issue: examining the directories in /opt/transmission-ui/transmission-web-control, I see they are all chmod 666:

> ll /opt/transmission-ui/transmission-web-control/tr-web-control:
total 48
drw-rw-rw- 6 root root 4096 Mar 28 08:00 ./
drwxr-xr-x 3 root root 4096 Apr  8 20:51 ../
-rw-rw-rw- 1 root root 1755 Mar 28 08:00 config.js
drw-rw-rw- 2 root root 4096 Mar 28 08:00 lang/
-rw-rw-rw- 1 root root 7341 Mar 28 08:00 logo-white.png
-rw-rw-rw- 1 root root 7257 Mar 28 08:00 logo.png
-rw-rw-rw- 1 root root  870 Oct 19  2017 plugin.js
drw-rw-rw- 5 root root 4096 Mar 30 00:50 script/
drw-rw-rw- 5 root root 4096 Mar 28 08:00 style/
drw-rw-rw- 2 root root 4096 Mar 28 08:00 template/

Running the following command inside my container fixed the UI:

find /opt/transmission-ui/transmission-web-control/ -type d -exec chmod 755 {} \;

BTW I love this UI, thank you!