Arch Linux

everwisher

Member

Registered: 2019-09-11

Posts: 33

Transmission webUI access only available for Firefox. Really weird...

I set up transmission-cli according to the instruction from ArchWiki and succeeded in invoking the daemon from webUI (192.168.1.* was added to the rpc-white-list in settings.json) on localhost, a lan peer and two virtual guests (Windows 10 + macOS) connected to the same network bridge as the host is.

Later, however, my success was proved to be exclusive to Firefox. All the other browsers, including Google Chrome (iOS, Windows and macOS), Safari (both iOS and macOS), Microsoft Edge and Internet Explorer, reported with complete blank webpage or ERR_CONNECTION_TIMED_OUT.

I just can't figure out why since I have no idea of web page technologies. Anyone has clue?

Last edited by everwisher (2020-01-12 02:19:46)

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: Transmission webUI access only available for Firefox. Really weird...

Is firefox still able to access it from the other devices ?
What URL are you giving the browsers ?

It could also be a network issue.

What is the ipv4 address of the host running transmission ?
If unsure, post ip a

Can you ping that address from the other devices ?

---

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

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

everwisher

Member

Registered: 2019-09-11

Posts: 33

Re: Transmission webUI access only available for Firefox. Really weird...

Is firefox still able to access it from the other devices ?
What URL are you giving the browsers ?

It could also be a network issue.

What is the ipv4 address of the host running transmission ?
If unsure, post ip a

Can you ping that address from the other devices ?

Thanks for your reply.

As a matter of fact, I have two physical machines running Arch as well as a bunch of virtual machines built up on them both. Every desktop version Firefox on each OS works well with http://192.168.1.2:9091 while all other browsers fail to do so, including Firefox for iOS (tried both on my phone and iPad).

Besides, if I set the rpc-white-list to "192.168.1.x (x indicates any one of my physical/virtual machines)" instead of "192.168.1.*", then no client can access the transmission-daemon via webUI. Can't figure out why either.

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: Transmission webUI access only available for Firefox. Really weird...

Hmm, does accessing non-https sites work from those other browsers ?

If unsure, try http://twokinds.keenspot.com/

Is dns over https enabled on those firefox desktop versions ?
Does firefox on iOS have a DoH setting ?

Are you running a firewall on the host ?

---

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

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

everwisher

Member

Registered: 2019-09-11

Posts: 33

Re: Transmission webUI access only available for Firefox. Really weird...

Hmm, does accessing non-https sites work from those other browsers ?

If unsure, try http://twokinds.keenspot.com/

Is dns over https enabled on those firefox desktop versions ?
Does firefox on iOS have a DoH setting ?

Are you running a firewall on the host ?

Yes I'm running ufw on the host and allow the Transmission app to communicate on 192.168.1.0/24 which is my local network. And that's proved by Firefox working.

I didn't enable DoH on any of these browsers explicitly though I don't know if any one use that as default. And I can find nowhere on Firefox iOS as to DoH settings.

All the browsers access non-https sites successfully. This is confirmed by testing.

Just now I upgraded the traditional Microsoft Edge to the latest released Chromium-based Edge, and it turned out to be the old story: ERR_CONNECTION_TIMED_OUT

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: Transmission webUI access only available for Firefox. Really weird...

There are multiple settings related to rpc with transmission , they could interfere.

If you're running the daemon as the transmission user , pease post /var/lib/transmission/.config/transmission-daemon/settings.json
Incase you're running transmission as you normal user, post ~/.config/transmission-daemon/settings.json

---

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

(A works at time B)  && (time C > time B ) ≠  (A works at time C)