I have my rutorrent client working, I can control rtorrent and download files.Only while connected to my LAN but I want to be able to access the webui from external networks. What would the best method to do this be?

Thanks

need to know your setup. I think you have a router and a local (home) network. Your client works within this home network and you wish to use it from outside. Probably you need to configure your router, but would be better to explain what do you really need.

Hi cnlh,

Building on pan64's post, in your home router, you need to port-forward an Internet-facing port (choose anything not in use) to the internal IP address and port you have assigned to the rtorrent webui.

Then from the Internet (outside your LAN), aim your browser at the external Internet-facing IP address of your home router, specifying the external port you chose (ex. http://200.200.200.1:35551) ... (replacing those values with your own ...).

Cheers.

sorry for the lack of information, it was late when I made the op. Im running rtorrent on ubuntu server 17.10 with rutorrent as the webui. I do have a router setup controlling the network. I have port 55000 forwarded for rtorrent but rutorrent doesn't have a port option itself as it's a frontend for rtorrent. I tried setting up a port forward for my external ip set to public port 55001 directed to the internal ip of my ubuntu server with internal port 55000. To access rutorrent internally I have to go to https:internalip/rutorrent. Any ideas, im fairly new to networking?

Hey again cnlh,

OK - I was assuming that you could set a separate port number for the webui ... I do this with qbittorrent. I am surprised this flexibility isn't offered - might be worth double checking.

You're using ssl internally (https), and ssl uses port 443. So you could try forwarding your external port 55001 to ip address:[internalip] port: 443.

.... or ... you could explore qbittorrent. I run it completely headless from a vm guest on a headless Arch server - so my only graphical interface is the webui - for which I can specify any port I like. Works great.

Cheers - let us know how you make out !

1 members found this post helpful.

I was using qbittorent, but switched to rtorrent...i forget why but I might switch back if I can get it to work. I'll try forwarding to 50001 to 443 whrn I am home. Thnaks for the help!

Just tested with qbittorent and it works as expected so I'm switching back. As I'm pretty bad with how networks work, how secure is having qbittorrent open like this. Does the login block brute force attacks by default?

Hi cnlh,

I run qbittorrent in a headless VM which I pause or shut down when not needed. Furthermore, I use as much of my router's security features as possible to discourage at least casual hackers (WPA2 encryption, non-broadcast of SSID, non-response to ICMP (pings), non-default internal IP address range, MAC filtering, non-standard TCP and / or UDP public and private ports .... ). So I guess the short answer to your question in my case, is "no". I wouldn't rely exclusively on the login for security.

Hope this helps - glad qbittorrent proved to be a solution for you.

Cheers !

I had the same problem - the only solution was to change default port 80 for web access to an another one - I just pick the 81. Don't forget to open this on your router.