Opened 7 years ago

Closed 7 years ago

#6013 closed Bug (invalid)

Remote whitelist does not work

Reported by: Jehan Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.84
Severity: Normal Keywords:
Cc:

Description

By default, the whitelist contains only 127.0.0.1, which should be ok if I only need the "remote" access to be in fact local (my case). So I click "Open web client" which tries and opens http://localhost:9091/ But then I get the "403: Forbidden" error:

Unauthorized IP Address.

Either disable the IP address whitelist or add your address to it.

I tried adding "localhost" (which should be the same as 127.0.0.1 anyway, but whatever, let's try) or even any other address which ifconfig tells me I have (though I would imagine that the origin address should always be 127.0.0.1 when this is also the destination). But it did not make anything better.

Only solution is to uncheck the whitelist (and putting login/password credential instad for some security).

Transmission 2.84 (14307) on Fedora 22.

Change History (3)

comment:1 Changed 7 years ago by simon.vetter

Try adding ::1 to the whitelist, I bet the 403 will go away.

::1 is the ipv6 address for localhost.

If that fixes your problem, Transmission should probably include it in the default ACL.

comment:2 Changed 7 years ago by Jehan

No it does not fix it. But I made a progress in diagnostic.

When I first tried to connect to the remote access today on http://localhost:9091, it just worked! No config changed, no "::1" added.

So I tried to uncheck then re-check "Allow remote access" to restart the remote server, and paf! "403: Forbidden" error again, like yesterday. Adding the "::1" did not fix the issue either.

Finally I quitted totally Transmission and restarted it. And it works again.

So a guess is that maybe the whitelist is not properly loaded when you start the remote access (checkbox "Allow remote access"), neither when you update the said whitelist, but it is only loaded at Transmission startup.

comment:3 Changed 7 years ago by x190

  • Resolution set to invalid
  • Status changed from new to closed

https://trac.transmissionbt.com/wiki/EditConfigFiles

Please use the forum for support issues. The daemon should stopped before editing the settings.json.

"So I tried to uncheck then re-check "Allow remote access" to restart the remote server, and paf! "403: Forbidden" error again, like yesterday. Adding the "::1" did not fix the issue either."

Yeah, but did you close the native WebUI and re-open it or try re-loading it?

If you still think this is a bug, please give step-by-step instructions to reproduce the issue and details of which type of Transmission you are using and on which OS, and then re-open the ticket.

Note: See TracTickets for help on using tickets.