Arch Linux

genji

Member

Registered: 2023-08-13

Posts: 61

[SOLVED] Problem with transmission-cli not addressed in the wiki

Hello, I followed the instructions, successfully I thought, in the arch wiki to install transmission-cli and it is running not as user transmission but as my regular user (and that worked fine too, with Arch Wiki's instructions - the transmission-daemon process is running as me now)

However, when I try to connect to the web interface, I am faced with a simple 403: Forbidden message?

The wiki mentions error 421, error 401, but never Error 403

The daemon is running, I can see it in the processes list, and I'm assuming web interface too because it's returning a 403 html error.

Thanks for any help!

Last edited by genji (2023-11-07 03:43:17)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,102

Re: [SOLVED] Problem with transmission-cli not addressed in the wiki

For clarity :

you are tying to connect to http://localhost:9091 ?

Which browsers have you tried with ?

Incase you use browser extensions like noscript , ublock origin, adblockers etc have you tried without them ?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,066

Re: [SOLVED] Problem with transmission-cli not addressed in the wiki

Hello, I followed the instructions

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Post exactly what you're running as well as the process tree ("ps fax") and then, as asked by Lone_Wolf, what url you're actually trying to open.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

genji

Member

Registered: 2023-08-13

Posts: 61

Re: [SOLVED] Problem with transmission-cli not addressed in the wiki

Sorry about that..  I finally tried this again with fresh eyes just now and solved it - I had to manually edit the settings.json file and inside the "rpc-whitelist" field add 192.168.1.*

Then I can access it now via https://192.168.1.X:9091 in my web browser from another device on my LAN

Thanks guys