RESOLVED: Transmission CLI Web interface 403 Forbidden

exup · 2024-07-01 06:41:18

The fix was that I had incorrectly edited the default transimssion.service file that although it allowed me to run transmission as a service under my user account this is not correct. So next time I upgraded it overwrote the service file and reset it. That meant transimssion was using the transmission service account and config.

As recommended use the drop in method descirbed here when editing service files.

https://wiki.archlinux.org/title/Systemd#Drop-in_files

Original post below

Hi, I recently performed system upgrade of my Transmission Container running Arch and Transmission CLI but I am not able to access the web interface. Pacman did not show any errors reported in the upgrade.
The message is "403 Forbidden" and nothing else its a blank page.

I see alot of posts about the RPC whitelist but as can be seen below it set to allow any ip address to access the site and was working.
I am accessing it on my local LAN and my ip address is local. I have tried from another device.

● transmission.service - Transmission BitTorrent Daemon
     Loaded: loaded (/usr/lib/systemd/system/transmission.service; enabled; preset: disabled)
    Drop-In: /run/systemd/system/service.d
             └─zzz-lxc-service.conf
     Active: active (running) since Mon 2024-07-01 15:37:33 AEST; 56min ago
 Invocation: 5ca30c7f818945739ff2130d1debd33c
   Main PID: 294 (transmission-da)
     Status: "Idle."
      Tasks: 3 (limit: 18978)
     Memory: 4.5M
        CPU: 4.612s
     CGroup: /system.slice/transmission.service
             └─294 /usr/bin/transmission-daemon -f --log-level=error

Jul 01 15:37:33 transmission systemd[1]: Starting Transmission BitTorrent Daemon...
Jul 01 15:37:33 transmission systemd[1]: Started Transmission BitTorrent Daemon.

and this is my settings.json file snippet I have tried rpc-whitelist-enabled both true and false in both cases it does not chage.

"rpc-authentication-required": false,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": true,
    "rpc-host-whitelist": "",
    "rpc-host-whitelist-enabled": true,
    "rpc-password": "edited out for the forum post",
    "rpc-port": 9091,
    "rpc-socket-mode": "0750",
    "rpc-url": "/transmission/",
    "rpc-username": "",
    "rpc-whitelist": "*.*.*.*",
    "rpc-whitelist-enabled": true,

Last edited by exup (2024-07-05 10:08:39)

cmm11 · 2024-07-01 13:44:03

"rpc-authentication-required": false,

Should that not be true ?

Lone_Wolf · 2024-07-01 14:00:05

Nope, I have that also and no issues .

Does specifically allowing localhost help ?

"rpc-whitelist": "127.0.0.1",

exup · 2024-07-02 03:30:19

Hi, if I understand correctly, I don't think I can test using local host as the machine is a headless server. So not able to open a browser on the local machine.

Lone_Wolf · 2024-07-02 12:47:24

Does transmission-remote host:9091 --session-info work ?
(replace host with the real name or ipaddress )

seth · 2024-07-02 13:08:05

not able to access the web interface. Pacman did not show any errors reported in the upgrade. The message is "403 Forbidden" and nothing else its a blank page.

1. what url do you try to access
2. is this a regression (same url worked previously)
3. Do you get access when passing the credentials to the url? http://login:password@host:9091/
4. Try the password that President Skroob uses on his suitcase

exup · 2024-07-02 22:24:39

Hi

1: URL is "http://192.168.0.9:9091/transmission/" the ip address is correct I can SSH into the box using that address, my shortcut I use all the time is "http://192.168.0.9:9091/transmission/web/#upload" and that does not work either
2. Yes regression the only thing I have done between it working and it stopping was performing "pacman -Syu" and it didnt show any errors. It did upgrade transmission.
3.The rpc-authenticaton-required was set to false, but I changed it to true and added an account. See below but it did not make any difference. Even if I put the wrong password or user in same response. "testuser:password@192.168.0.9:9091/transmission"

Note I am stopping the transmission and starting it every time I make a change. Plus I have put everything back to what is was before. (remove the authentication and passwords etc.

    "rpc-authentication-required": true,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": true,
    "rpc-host-whitelist": "",
    "rpc-host-whitelist-enabled": true,
    "rpc-password": "password",
    "rpc-port": 9091,
    "rpc-socket-mode": "0750",
    "rpc-url": "/transmission/",
    "rpc-username": "testuser",
    "rpc-whitelist": "*.*.*.*",
    "rpc-whitelist-enabled": true,

● transmission.service - Transmission BitTorrent Daemon
     Loaded: loaded (/usr/lib/systemd/system/transmission.service; enabled; preset: disabled)
    Drop-In: /run/systemd/system/service.d
             └─zzz-lxc-service.conf
     Active: active (running) since Wed 2024-07-03 07:57:16 AEST; 3s ago
 Invocation: 4374aae9782e49cfb81f2aac563d3e73
   Main PID: 513 (transmission-da)
     Status: "Uploading 0.14 KBps, Downloading 0.14 KBps."
      Tasks: 4 (limit: 18978)
     Memory: 2.1M
        CPU: 21ms
     CGroup: /system.slice/transmission.service
             └─513 /usr/bin/transmission-daemon -f --log-level=error

Jul 03 07:57:16 transmission systemd[1]: Starting Transmission BitTorrent Daemon...
Jul 03 07:57:16 transmission systemd[1]: Started Transmission BitTorrent Daemon.

exup · 2024-07-02 22:32:01

Lone_Wolf wrote:

Does transmission-remote host:9091 --session-info work ?
(replace host with the real name or ipaddress )

I tried on the host machine (server)

transmission-remote 192.168.0.9:9091 --session-info
Unexpected response: <h1>403: Forbidden</h1>

then used local host address which worked, cant see any info that points to an issue.

VERSION
  Daemon version: 4.0.6 (38c164933e)
  RPC version: 17
  RPC minimum version: 14

CONFIG
  Configuration directory: /var/lib/transmission/.config/transmission-daemon
  Download directory: /var/lib/transmission/Downloads
  Listenport: 51413
  Portforwarding enabled: Yes
  µTP enabled: Yes
  Distributed hash table enabled: Yes
  Local peer discovery enabled: Yes
  Peer exchange allowed: Yes
  Encryption: preferred
  Maximum memory cache size: 4.00 MiB

LIMITS
  Peer limit: 200
  Default seed ratio limit: Unlimited
  Upload speed limit: Unlimited (Disabled limit: 100 kB/s; Disabled turtle limit: 50 kB/s)
  Download speed limit: Unlimited (Disabled limit: 100 kB/s; Disabled turtle limit: 50 kB/s)

MISC
  Autostart added torrents: Yes
  Delete automatically added torrents: No

seth · 2024-07-03 06:04:15

https://gitlab.archlinux.org/archlinux/ … 9f833ed9f3
But the IP is a LAN segment… does downgrading transmission and miniupnpc restore the expected behavior?

exup · 2024-07-03 10:39:06

OK I downgraded the transmission package and it started to work ok.
So then I upgraded it back to current version, but it didnt work

Now I run the transmission service as my own user account as my config is under my profile.

So I normally just edit the ./multi-user.target.wants/transmission.service file and change the user from transmission to my user account.
Save it
then systemctl daemon-reload
systemctl restart transmission.serivice
systemctl enable transmission.serivce

I think what has happened between the version is the transmission.service file was removed and recreated in a new location and using a different account "transmission" which uses a different .config file which probably was not allowing me to access it via the web. So all the changes in my config file where not being referenced.

I found the new service file is here.
/usr/lib/systemd/system/transmission.service and sure enough it was using the User=transmission
I have edited and now its using my .config

Last edited by exup (2024-07-03 11:15:39)

seth · 2024-07-03 13:01:49

So I normally just edit the ./multi-user.target.wants/transmission.service file and change the user from transmission to my user account.

Don't.
https://wiki.archlinux.org/title/System … ided_units

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

exup · 2024-07-05 04:24:59

Ah OK, so when I have manually edited this file, then I upgraded, PACMAN just over wrote it. Where in your link I needed to create a new unit file which will over ride it, including future upgrades I take it.
Something I will make a note of in future thanks.

But what is meant with second half of the comment, future system maintenance is more difficult?

Note: The replacement units will keep on being used even if Pacman updates the original units in the future. This method makes system maintenance more difficult and therefore the next approach is preferred.

seth · 2024-07-05 06:23:55

If the service file changes with the update, that change will be silently ignored if the file is locally shadowed, while the augmentating drop-in will pick up that change.

seth wrote:

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

exup · 2024-07-05 09:58:24

OK thanks for the help in sorting this out, I ll mark it RESOLVED

Arch Linux

#1 2024-07-01 06:41:18

RESOLVED: Transmission CLI Web interface 403 Forbidden

#2 2024-07-01 13:44:03

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#3 2024-07-01 14:00:05

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#4 2024-07-02 03:30:19

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#5 2024-07-02 12:47:24

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#6 2024-07-02 13:08:05

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#7 2024-07-02 22:24:39

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#8 2024-07-02 22:32:01

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#9 2024-07-03 06:04:15

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#10 2024-07-03 10:39:06

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#11 2024-07-03 13:01:49

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#12 2024-07-05 04:24:59

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#13 2024-07-05 06:23:55

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

#14 2024-07-05 09:58:24

Re: RESOLVED: Transmission CLI Web interface 403 Forbidden

Board footer