Transmission

Hello there,

I just started playing around with the web interface and everything is working fine in my LAN. However, I can't get the remote access to work.

I created a dyndns.org account which is working (I get to my router's administration page) and I set up port forwarding for port 9091 (http://www.canyouseeme.org/ tells me that the port is open). However, when I go to mydomain.dyndns.org:9091 I only get a "could not open site" error. Is there anything else I might try? Is there a possibility to add the LAN-IP (192.168.1.2) to the dyndns-address so that my router knows where to "put" the request? Any ideas?

Thanks in advance!

It could be that the router is not properly forwarding the port to the device.
It could also be that there is some sort of access control either on the router or your device that blocks the request.

Also that he's not using NAT or PNAT and servers don't work outside the LAN.

Like the old movie used to say "what we have here... is a problem of communication" (Cool Hand Luke), not a Transmission problem.

Thanks for your answers. I finally found out that the access to the web interface does work from the internet. Yesterday, I only tried to access it from my LAN trough the external dyndns-address which didn't work (for whatever reason). But when I try to access it from another network over the internet it works seamlessly.

gaddagah wrote:I only tried to access it from my LAN trough the external dyndns-address which didn't work (for whatever reason).

The reason is simple: your dyndns address is your external IP address, inside the LAN your server has a different (internal, private) address. Unless your DNS server is smart enough to manage split views, you can't use the external name inside the LAN...

Hi Gurus..

I too am experiencing a problem with accessing Transmission outside my network. I CAN access it with my external ip address, as well as the dyndns.org account I set up. ONLY if i have the ip address from the computer I'm using included in my settings.json file.

Since this can change, I would have to update the settings.json file with whatever my ip address is on the laptop I use remotely to connect.

I'm sure I'm missing something... I'd appreciate any help..

tanstaafl1963 wrote:I CAN access it ... ONLY if i have the ip address from the computer I'm using included in my settings.json file.

Since this can change, I would have to update the settings.json file with whatever my ip address is on the laptop I use remotely to connect.

In the default configuration you'll see this: Or similar, perhaps the first line already includes your LAN as something like 192.168.*.*; you can disable the white-list changing the second line (from true to false) or the equivalent which would be adding all IP addresses to the first line, 0.0.0.0 might work (I haven't tested), some people use *.*.*.* (which I also haven't tested).

Either way, you can keep the authentication-required setting enabled so that the daemon will only allow access to people who know the user/password.

There are equivalent parameters that can be passed to the daemon at start-up (-a "127.0.0.1,192.168.10.*" -t -u admin_user -v admin_passwd) but if the white-list is already enabled I think the daemon will take what settings.json says so you cannot disable it on the parameters.

Also remember that changing settings.json permanently only works if you stop the daemon before making any changes.

rb7,
Thanks for the reply... this makes sense..

and even better.. I got it working

I appreciate it..