Jump to content

dvd.collector

Members
  • Content Count

    259
  • Joined

  • Last visited

Posts posted by dvd.collector


  1. So I've tried every endpoint in the PIA list and all throw this:
     

    2020-09-09 10:39:03,388 DEBG 'start-script' stdout output:
    [info] List of PIA endpoints that support port forwarding:-
    [info] ca-toronto.privateinternetaccess.com
    [info] ca-montreal.privateinternetaccess.com
    [info] ca-vancouver.privateinternetaccess.com
    [info] de-berlin.privateinternetaccess.com
    [info] de-frankfurt.privateinternetaccess.com
    [info] france.privateinternetaccess.com
    [info] czech.privateinternetaccess.com
    [info] spain.privateinternetaccess.com
    [info] ro.privateinternetaccess.com
    [info] israel.privateinternetaccess.com
    [info] Attempting to get dynamically assigned port...
    
    2020-09-09 10:39:24,196 DEBG 'start-script' stdout output:
    [warn] Exit code '52' from curl != 0 or no response body received
    [info] 12 retries left
    [info] Retrying in 10 secs...
    
    2020-09-09 10:39:24,196 DEBG 'start-script' stdout output:
    [warn] Exit code '52' from curl != 0 or no response body received
    [info] 12 retries left
    [info] Retrying in 10 secs...

     

     

    Is PIA removing port forwarding ability completely?

     

    If so, is there a different VPN that supports port forwarding that anyone would recommend?

     

     

    EDIT, saw this on the PIA website:
    * The information contained within this article will only work with our Current/Previous Generation servers. Our Next Generation servers do not currently offer port-forwarding outside of the application. *

     

    So I guess as they upgrade their servers this will stop working.  Back to my other question then, can anyone recommend a different VPN that will work well with this docker?


  2. On 7/22/2020 at 1:24 PM, binhex said:

    yes, as the log says, pia vpn api not accessible, i would assume only for this endpoint (france), try another of the ones listed in the log. 

     

    OK I switched to Germany and it seems to work now.

    • Like 1
    • Thanks 1

  3. On 7/20/2020 at 10:19 AM, binhex said:

    Attached log.  I am assuming that this is the issue:

     

    [warn] Unable to download file from url 'http://209.222.18.222:2000/?client_id=b911029a01c805dd6c6d72c547ed627e84ec450593a5c59d3a94bbd10f4cff5a', exiting script...
    [warn] PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port...

     

     

    Is this a PIA problem?

    supervisord - clean.log


  4. Hi all,

     

    this container has been working fine for me for ages, but in the last couple of days I've been seeing this error:

     

    2020-07-20 09:39:43,246 DEBG 'start-script' stdout output:
    [info] Attempting to get dynamically assigned port...
    
    2020-07-20 09:39:43,372 DEBG 'start-script' stdout output:
    [warn] Exit code '56' from curl != 0 or no response body received
    [info] 12 retries left
    [info] Retrying in 10 secs...
    
    2020-07-20 09:39:53,431 DEBG 'start-script' stdout output:
    [warn] Exit code '52' from curl != 0 or no response body received
    [info] 11 retries left
    [info] Retrying in 10 secs...
    
    ...
    
    2020-07-20 09:41:44,100 DEBG 'start-script' stdout output:
    [warn] Exit code '56' from curl != 0 or no response body received, exhausted retries
    
    2020-07-20 09:41:44,101 DEBG 'start-script' stdout output:
    [warn] Unable to download file from url 'http://209.222.18.222:2000/?client_id=d69a030e782a094400b7a58b95cd54440c69b881358170e6b28ea3c437f4f223', exiting script...
    
    2020-07-20 09:41:44,101 DEBG 'start-script' stdout output:
    [warn] PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port...
    
    2020-07-20 09:41:44,102 DEBG 'start-script' stdout output:
    Mon Jul 20 09:41:44 2020 event_wait : Interrupted system call (code=4)

    Neither privoxy or rtorrent works.

     

    Any ideas what is causing this?


  5. 1 hour ago, testdasi said:

    That would have been right 5-10 years ago but it's not true any more.

    Even back when RDP didn't work with games, GPU hardware acceleration still worked.

     

    You can now play games via RDP on Windows 10 (it was also reported to work with Windows 8 but I don't have any Windows 8 machine to test).

    • Not all games will work. Some games work but buggy e.g. audio issues.
    • Latency is ok but don't expect to play twitchy FPS
    • Graphics performance is more like watching a movie (think 24fps) so again no twitchy stuff

     

    Don't expect to use Teamviewer for free. Their free for personal uses policy is a scam because they can arbitrarily say "commercial use detected" and force you to pay for it. Just google "Teamviewer commercial use detected" and fine the comically long complaint topic about this issue, for which Teamviewer can't even bother to respond.

     

    Even if let's say RDP doesn't work, there are so many free alternatives out there such as NoMachine, Parsec, even VNC just to name some.

    But note that remote desktop is still remote desktop. If you expect to be just like you are sitting next to the workstation then you will be disappointed.

     

    It may be different by application I suppose, but I'm using win10 physical machine to a win10 vm (with an nvidia GPU passed through) and when using RDP the gpu is not detected for hardware encoding in Resolve (or Powerdirector).   Using teamviewer it is.

     


  6. Has anyone had issues with Sonarr not automatically starting when the array starts recently.  All was fine until a couple of days ago and now Sonaar will not auto start.

     

    It starts fine if I go and manually choose start from the menu....

     

    Am unsure exactly which parts of the log are current as it doesn't seem to create a new log when it starts, but these are the last entries from when it does not startup.

     

    [cont-finish.d] executing container finish scripts...
    [cont-finish.d] done.
    [s6-finish] syncing disks.
    [s6-finish] sending all processes the TERM signal.
    [s6-finish] sending all processes the KILL signal and exiting.

     


  7. OK so when I click on Cache, I can change that to btrfs.   When I click on cache2, it says "unknown" in partition format.

     

    Went ahead and changed Cache to btrfs anyway then clicked format.

     

    It looks like this worked (see screenshot).

     

    Now just need to change to raid 0 i guess.

    error2.jpg


  8. OK, so I stopped the array, ran the blkdiscard command on both disks, restarted array but see the same error message.

     

    Should I have removed them as cache drives first?  I'll try that now anyway.


  9. I want to use two ssd's in a raid 0 configuration as a cache drive.

     

    I created a RAID0 array in the bios of my unraid server, however unraid does not seem to see that - it still sees the individual disks.   Is this expected?


  10. 20 hours ago, binhex said:

     

    its already fixed guys :-), go back to latest.

     

    edit FYI - the issue was due to a bump in the rtorrent version, this makes some of the older style options in the rtorrent.rc invalid, and thus for now they have been removed. i would encourage all users to consider moving to the newer style rtorrent.rc file otherwise there maybe breakage in the future, instructions below:-

     

    1. rename file /config/rtorrent/config/rtorrent.rc to rtorrent.rc.old

    2. restart container

    3. copy values for anything non default (do not copy keys such as 'use_udp_trackers') in rtorrent.rc.old to the newly geneated rtorrent.rc file

    4. restart container and ensure it starts correctly

    5. once happy delete file /config/rtorrent/config/rtorrent.rc.old

     

    IMPORTANT - Please ensure the editor you use sets the line endings to LF and NOT CRLF for the rtorrent.rc file.

     

     

    Hmm, I've updated the container to the latest and still can't get to rutorrent, just seems to be looping trying to start.  Privoxy works fine.


  11. From my observations, the gpu does power down when not in use, however it isn't completely off.

     

    When I start a VM that uses the GPU the power consumption (measured at the wall) jumps 100-200watt, even with the vm idle doing nothing.  My assumption is that this is the GPU drawing power as the consumption before starting a VM is around 70watt which seems too low if it included GPU draw.

     

    The fans on the GPU are on though, so it must be actually powered up.

     

    This is an AMD RX480 so its entirely possible that newer GPU's have a way of "powering down" when not in use which older ones do not.


  12. Ah how did I miss that...!  Thanks, changed to France and its working now.

     

    I think I was confused as I had a different issue related to PIA as well.  I could not access their website due to the SSL_PROTOCOL_ERROR.   After googling it seems this is related to my ISP's WEBSAFE filter, which seems to have started causing issues with PIA from yesterday.

     

    After disabling the WEBSAFE filter on my ISP account settings I can now access the PIA website again.

     

    Seems too co-incidental that both issues happen at once, but maybe i'm just unlucky!


  13. Is anyone having issues with PIA today?

     

    Suddenly this docker will not work and I cannot access the PIA website (from another pc) which throws the error ERR_SSL_PROTOCOL_ERROR.

    The docker log seems to show this error over and over again:

    2018-04-03 11:03:00,913 DEBG 'start-script' stdout output:
    [info] Attempting to curl http://209.222.18.222:2000/?client_id=3663b5f1cc355a121364e709954f045c7b1bc67d6aabf721ee1eb382e30aa751...
    
    2018-04-03 11:03:00,946 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 12 retries left
    [info] Retrying in 10 secs...
    
    2018-04-03 11:03:00,980 DEBG 'start-script' stdout output:
    [info] Successfully retrieved external IP address 212.92.117.185
    
    2018-04-03 11:03:10,975 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 11 retries left
    [info] Retrying in 10 secs...
    
    2018-04-03 11:03:21,013 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 10 retries left
    [info] Retrying in 10 secs...
    
    2018-04-03 11:03:31,040 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 9 retries left
    [info] Retrying in 10 secs...
    
    2018-04-03 11:03:41,072 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 8 retries left
    [info] Retrying in 10 secs...
    
    2018-04-03 11:03:51,099 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 7 retries left