Jeffarese

Members
  • Content Count

    47
  • Joined

  • Last visited

Posts posted by Jeffarese

  1. On 3/3/2021 at 10:26 AM, Jeffarese said:

    I just updated and port forwarding seems to have some problems. It was working perfectly before the update  (in multiple docker containers using different PIA endpoints).

     

    Everything seems to be OK in the logs. It retrieves the port from the PIA endpoint:

     

    
    2021-03-03 09:25:45,174 DEBG 'watchdog-script' stdout output:
    [info] rTorrent incoming port 49160 and VPN incoming port 36936 different, marking for reconfigure

     

    Then, after:

     

    
    2021-03-03 09:26:04,357 DEBG 'watchdog-script' stdout output:
    [info] ruTorrent plugins initialised

     

    The logs start outputing this:

     

    
    2021-03-03 09:40:44,618 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '36936'
    
    2021-03-03 09:55:44,787 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '36936'
    
    2021-03-03 09:56:24,526 DEBG 'watchdog-script' stdout output:
    [info] rtorrent incoming port closed, marking for reconfigure
    
    2021-03-03 10:10:44,958 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '36936'

     

    However, the port shows as "Closed" in the UI (red exclamation mark) even after hours. 

    Also, my clients were pretty consistent in the upload per day (around 500GB per day, sometimes some container would upload 1TB) and the last day I only upload between 5 - 30GB (and some of them less than 1GB), so clearly there's something not there yet.

     

    I'm using Wireguard with `privileged=true`. All was working before this update. I think the last time I updated was 1-2 months ago, I'm not sure, but I was already using wireguard and everything was working fine.

     

    I'm still having this problem. I updated again and the problem persists:

     

    Ports don't seem to be forwarded or configured in rTorrent correctly:

     

    2021-03-08 11:34:04,443 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '22390'
    
    2021-03-08 11:49:04,604 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '22390'
    
    2021-03-08 11:53:23,017 DEBG 'watchdog-script' stdout output:
    [info] rtorrent incoming port closed, marking for reconfigure
    
    2021-03-08 12:04:04,769 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '22390'
    
    2021-03-08 12:19:04,932 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '22390'
    
    2021-03-08 12:23:30,398 DEBG 'watchdog-script' stdout output:
    [info] rtorrent incoming port closed, marking for reconfigure
    
    2021-03-08 12:34:05,103 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '22390'
    
    2021-03-08 12:49:05,273 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '22390'
    
    2021-03-08 12:53:37,361 DEBG 'watchdog-script' stdout output:
    [info] rtorrent incoming port closed, marking for reconfigure
    
    2021-03-08 13:04:05,445 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '22390'
    
    2021-03-08 13:19:05,617 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '22390'

     

    Any ideas?

  2. I just updated and port forwarding seems to have some problems. It was working perfectly before the update  (in multiple docker containers using different PIA endpoints).

     

    Everything seems to be OK in the logs. It retrieves the port from the PIA endpoint:

     

    2021-03-03 09:25:45,174 DEBG 'watchdog-script' stdout output:
    [info] rTorrent incoming port 49160 and VPN incoming port 36936 different, marking for reconfigure

     

    Then, after:

     

    2021-03-03 09:26:04,357 DEBG 'watchdog-script' stdout output:
    [info] ruTorrent plugins initialised

     

    The logs start outputing this:

     

    2021-03-03 09:40:44,618 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '36936'
    
    2021-03-03 09:55:44,787 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '36936'
    
    2021-03-03 09:56:24,526 DEBG 'watchdog-script' stdout output:
    [info] rtorrent incoming port closed, marking for reconfigure
    
    2021-03-03 10:10:44,958 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '36936'

     

    However, the port shows as "Closed" in the UI (red exclamation mark) even after hours. 

    Also, my clients were pretty consistent in the upload per day (around 500GB per day, sometimes some container would upload 1TB) and the last day I only upload between 5 - 30GB (and some of them less than 1GB), so clearly there's something not there yet.

     

    I'm using Wireguard with `privileged=true`. All was working before this update. I think the last time I updated was 1-2 months ago, I'm not sure, but I was already using wireguard and everything was working fine.

  3. Is there any recent change regarding auto opening ports with PIA VPN? 

    Since I started using PIA the incoming port used on rTorrent was automatically changed after a while on rTorrent to match the port forwarded provided by PIA api.

    Since a few days ago I've seen that the red mark is present on all torrent clients and I don't seem to get lots of connections, so it seems that the ports are not being set indeed.

     

    Just to clarify: The port used in ruTorrent does not seem to be updated with the forwarded port reported by the rtorrent log when retrieving it from PIA API.

    Log trailing with:

     

    Quote

    2020-08-24 21:50:08,194 DEBG 'watchdog-script' stdout output:
    [info] rtorrent incoming port closed, marking for reconfigure
    2020-08-24 22:20:21,572 DEBG 'watchdog-script' stdout output:
    0
    2020-08-24 22:20:25,412 DEBG 'watchdog-script' stdout output:
    [info] rtorrent incoming port closed, marking for reconfigure
    2020-08-24 22:50:33,843 DEBG 'watchdog-script' stdout output:
    0
    2020-08-24 22:50:36,721 DEBG 'watchdog-script' stdout output:
    [info] rtorrent incoming port closed, marking for reconfigure

     

  4. 10 minutes ago, binhex said:

    correct, you dont need to forward ports but you do still need a port to connect to rutorrent web ui, and this will have to be unique for each container, change only the host side NOT the container port.

    Ah yes! I already had this setup in the past, I have that sorted out :) Thanks!

  5. lol sorry, my mind was in another place. Yeah, I meant of your image :P
    Each one of the containers are using different PIA servers (endpoints) so each one of them receive a different IP & request a different port, even though all the containers are running in the same server.

     

    How would I have host port conflicts? I don't need to forward host ports since the ports are open by the VPN, right?

  6. 13 minutes ago, binhex said:

    yes, leave the container running and it will sort it all out for you, i just had my port close (vpn provider issue) and my scripts kicked in to reconfigure for a new incoming port automagically.

    Correct! it sorted it out after a while and now it shows green!

     

    Unrelated question about PIA:

    Is there any problem if I have multiple instances of your script using different server configs (one container has sweden.ovpn, another one has france.ovpn) so each one of the containers requests a different port?
    I run multiple containers of your image to organize better my files.
    It seems to be working OK and all of them show the green icon now and seem to be seeding ok.

  7. Is the auto port assign of PIA working correctly?

     

    I see the messages in the logs about retrieving and assigning the port from PIA:

     

    [info] Successfully assigned incoming port 55730
    [info] Checking we can resolve name 'www.google.com' to address...
    [info] DNS operational, we can resolve name 'www.google.com' to address [REDACTED]
    [info] Attempting to get external IP using Name Server 'ns1.google.com'...
    [info] Successfully retrieved external IP address [REDACTED]
    [info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP [REDACTED]different, marking for reconfigure
    [info] rTorrent not running
    [info] rTorrent incoming port 49160 and VPN incoming port 55730 different, marking for reconfigure

    However, the port reported in the interface bottom bar is a different one (the one I had previosuly configured) and it shows the red icon saying the port is not open.

  8. On 10/16/2019 at 6:57 AM, ljm42 said:

    In the future it may be possible to restrict it so that only specific Dockers use the VPN tunnel.  Until then, you may need to disable the tunnel in order to check for plugin updates or perform other Unraid administrative tasks.

    Any aproximation to when is this going to be possible aprox? This would be the killer feature, since routing ALL the traffic seems like a little bit too much.

     

    Thanks!

  9. Hey, one question.

     

    Given that I'm running in a more or less powerfull machine (R9 3900x, 64GB RAM), with plenty of resources, is there any settings/tweaks that can be done to increase the performance further? 

     

    I'm currently sitting at 1700 torrents and sometimes I get timeouts, it seems that nginx can't handle it that well (even if rTorrent itself is a beast)

  10. 1 hour ago, binhex said:

    probably cos you exec'd in as user root not user 'nobody', im assuming you have enabled irssi right?.

    Ah yeah, that seems to be the problem. 

    In order to access the container I do

     

    docker exec -it binhex-rtorrentvpn /bin/bash

     

    That logs me in as root.

     

    How is the normal procedure to access it as nobody?

     

    just

     

    docker exec -it --user nobody binhex-rtorrentvpn /bin/bash?

     

  11. Jackett was auto updated and a segfault appeared in logs:

     

    Oct 24 02:07:54 Orthanc Docker Auto Update: Stopping jackett
    Oct 24 02:07:54 Orthanc kernel: jackett[15933]: segfault at 10 ip 000015497d9b8fa0 sp 00007ffcf94158d8 error 4 in libpthread-2.27.so[15497d9af000+1a000]
    Oct 24 02:07:54 Orthanc kernel: Code: 07 00 00 00 48 89 df b8 ca 00 00 00 0f 05 64 48 c7 04 25 f0 02 00 00 00 00 00 00 b8 83 00 00 00 e9 a8 fb ff ff 0f 1f 44 00 00 <8b> 47 10 89 c2 81 e2 7f 01 00 00 90 83 e0 7c 0f 85 9b 00 00 00 48
    Oct 24 02:07:57 Orthanc kernel: veth13798ed: renamed from eth0
    Oct 24 02:07:57 Orthanc kernel: br-d45ab5905980: port 10(veth98599ed) entered disabled state
    Oct 24 02:07:57 Orthanc kernel: br-d45ab5905980: port 10(veth98599ed) entered disabled state
    Oct 24 02:07:57 Orthanc kernel: device veth98599ed left promiscuous mode
    Oct 24 02:07:57 Orthanc kernel: br-d45ab5905980: port 10(veth98599ed) entered disabled state
    Oct 24 02:07:57 Orthanc Docker Auto Update: Stopping lidarr
    Oct 24 02:08:01 Orthanc kernel: veth3683ba0: renamed from eth0
    Oct 24 02:08:01 Orthanc kernel: br-d45ab5905980: port 5(vethd40c869) entered disabled state

     

    Everything works fine (as far as I can tell), but I'm worried about seeing a segfault on the logs. Anybody knows what could be happening?

     

     

    Attached diagnostics

    orthanc-diagnostics-20191024-0547.zip

  12. What MariaDB container?

     

    The problem is that there are two shares.

     

    One where you store the config, which should be on cache.

     

    The other where you store the data, which obviously is in the array.

     

    This was created in a way that the owncloud.db is on the share that you need to store in the array.

  13. Hello,

    I'm upgrading a server I have at home and I'm looking at Epyc & Threadripper CPUs.

    My needs are:

    1 VM as main development server which also acts as CI/CD running tests

    Multiple VMs for testing

    VPN & firewall

    Media center (automation with Plex, Sonarr, Radarr...etc)

    I currently have aprox 80TB and I'm planning on keep increasing this storage a lot, so I need plenty of room for storage expansion.

    I also need to have some NVMe drives in RAID 0 / 10 for some very intensive IO tasks.

    I do NOT need GPU power.

    Looking at the new Epyc 7002 series they actually seem cheaper than current Threadrippers, the only thing it's holding me back in that regard is that at least here in Europe Epyc motherboards are pretty hard to get get.


    Also, is there any reason to chose Threadripper over Epyc in my use case? high frequency is not needed for my use case at all, so I think it would be a waste of power.

    In any case, which boards would you recommend? Anybody have similar setups?

    Thanks!