[[Support] binhex - rTorrentVPN]

1 hour ago, binhex said:

it doesn't matter whatsoever, if you have confirmed the port is open using an external website then thats all the confirmation you should need.

 

having said that i have no issues at all with the built in indicator in rutorrent and it is always green, unless PIA has a wobble, in which case it may go red temporarily before my script kicks it and corrects the issue (restarts openvpn).

it tests the incoming port as defined in rutorrent, it uses an external website (https://portchecker.co) to do the check (web scrape) and if the port is open then it is green, if not then its red, and if it cannot contact the website then it is orange, i use the same website to do my own internal check, and it always reports the correct status to me.

 

Thank you for the explanation. As explained I don't use PIA but another VPN provider so i'm using custom preset. The ovpn file work like a charm, eveyrthing seems ok. Still have the red mark at the bottom, like you told I have confirmation from curl within the docker container the port is open. I have test the op against your website using VPN shared ip i'm assigned to and the port is Open. 

Rtorrent is still red. But I shouldn't care, it's just mental. 
Thank you again for your image, best. 

[[Support] binhex - rTorrentVPN]

On 8/13/2020 at 6:46 PM, Cull2ArcaHeresy said:

does your vpn have port forwarding? i use pia and sometimes pia and rtorrent will pick the same port and it will show open, but most the time it shows closed. If i found the list of pia port ranges again (but was old list so prob bad) i would set my range to match, but be it pia or something else, port open or closed i get the same connection where it will be full speed for a while now and then but most the time it is <1m up/down. i did not buy pia for this, already had it.

Honestly i've the same case here, image is running fine, port is forwarded (confirmed by port check from vpn provider with curl). Still red and closed. But it's working fine on download (dunno for up btw). I just don't know if it matters to have the green mark in rutorrent gui that tells you the port is open. I really don't know how it works inside the container. Honestly i've seen this green while I have my config broken (couldn't ssl private tracker by example) so afaik it doesn't tell you rtorrent is working it just tells you a port is open or not to listen connection but it's within the container... so... what does it test because it can't really test vpn port isn't it ? 

[[Support] binhex - rTorrentVPN]

22 hours ago, erqzor said:

Hello there,

 

First thanks to binhex for his work. I've found this image the easiest way to setup secured rtorrent container in a blink.
Everything is well explained but I'm stuck at the reverse proxy stage. I have an almost working setup, able to connect to local_ip:port from a local computer, i'm facing a 404 when using domain.tld/rutorrent and hitting my nginx reverse proxy.

I've found the tip about php file (nginx into the container and nginx as reverse proxy). 

I've just remarked one thing that could explain I've misconfigured something (unfortunately I don't have logs on this computer ; but I could provide them later), it tries to hit path_to_rutorrent/rutorrent/rutorrent/. 

Will be glad to read something I've missed into documentation that could help to solve this issue. Note that i have linuxserver/letencrypt + organizr-v2 + tautulli + ombi working well with sso enabled so I consider my nginx configuration maybe not so bad. 

Thank you for any ideas, 

Hello, 

I've found my issue, so I'm sharing the issue resolution and some tips for beyond.

 

1- You must follow the installation guide (strictly, yes!, seriously, strict).
2- You must ensure the vpn settings are correct on server side (I've waste a lot of time, when the solution was into the .ovpn file)
3- You have to dig supervisor.log to find issue.

4- I didn't figure out how to make sso working between rtorrent/rutorrent - organizr (dunno if in fact its possible)
5- Bonus : if you are facing torrent client issue to connect to private tracker, double check your vpn settings, the issue is there (certainly ssl connection breaks; check vpn provider docs; adjust mtu)

 

Thank you binhex for the amazing work. 

[[Support] binhex - rTorrentVPN]

Hello there,

 

First thanks to binhex for his work. I've found this image the easiest way to setup secured rtorrent container in a blink.
Everything is well explained but I'm stuck at the reverse proxy stage. I have an almost working setup, able to connect to local_ip:port from a local computer, i'm facing a 404 when using domain.tld/rutorrent and hitting my nginx reverse proxy.

I've found the tip about php file (nginx into the container and nginx as reverse proxy). 

I've just remarked one thing that could explain I've misconfigured something (unfortunately I don't have logs on this computer ; but I could provide them later), it tries to hit path_to_rutorrent/rutorrent/rutorrent/. 

Will be glad to read something I've missed into documentation that could help to solve this issue. Note that i have linuxserver/letencrypt + organizr-v2 + tautulli + ombi working well with sso enabled so I consider my nginx configuration maybe not so bad. 

Thank you for any ideas,