Jump to content

Alias

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by Alias

  1. On 5/21/2020 at 2:09 PM, glompy said:

    I have fiber with google nest router, I've never had an issue with it, but I wouldn't know how to go about testing if google is actively doing something there. That said, I do have VPN connections for work that I leave up all the time and those do not get terminated, so unless they are actively dropping connections to known PIA servers? However I figured they would have done that with the socks5 proxy too.

     

    In any case, I signed up for another VPN provider... and it is night and day difference already, port forwarding took a minute to set up, but already getting double the bandwidth though the torrents. Its only been up for 2 hours, but I will be watching it. It will be much nicer to have dedicated ports as well now, so I'm probably just going to stick with it.

     

    Still getting the occasional ruTorrent timeout, logs mentioned earlier, on localhost:5000 (netdata reports cpu usage for the container never goes above 4% in the last 24 hours), so I stopped navigating to the built-in ruTorrent and installed a flood-ui container to access rTorrent. ruTorrent still times out and is not usable, but flood continues to work just fine. Not quite sure how to debug that.

     

     

    Edit::

     

    Not a single disconnect in over a day. Looks like I will be dropping PIA like a hot rock and staying with this new vpn provider when it comes to torrents :)

    Which other VPN provider did you switch to? I also keep getting port closed on PIA after working a while so I thinking this is something on PIA's end

  2. 11 hours ago, Einsteinjr said:

    Is there anyone else facing an issue where the port status is unknown?  I haven't changed anything and all-of-a-sudden it has gone back to that.

     

    No VPN and I've confirmed port-forwarding is working.

     

    Thanks in advance.

    Same here. Having the same issue. Are you using PIA as VPN?

  3. I have been using PIA with the docker image and it has been going well so fine. But recently I have noticed (since I updated the docker image recently or not sure if this is due to PIA) that my port forward status keeps going red (port closed) after about a few hours since the container started. 

     

    Is this normal? Or is this something on the PIA side where they keep closing an open port after a while?

×
×
  • Create New...