tuna83

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by tuna83

  1. I've been troubleshooting this on and off for the past 2 weeks. would love to work it out by myself but am turning here for help in the end.

     

    I'm new to pfsense so I assumed it was an issue with my knowledge there, but I think it's down to checking that the docker is working on my end properly. I'm having some issues getting the server connected from external IP's. I'm sure it's a port issue. I can access the game if I use the local address 192.168.0.101:26900, but can't using the external one.

     

    Using the diagnostics from the router it seems the docker isn't actually listening on port 26901/26092/26093/27015. Is that right?

     

    I opened the ports listed in this wiki page: https://developer.valvesoftware.com/wiki/7_Days_to_Die_Dedicated_Server#Firewall_Ports as I couldn't find anything concrete specific to the docker container, and it correlates with the container ports

    Quote

    Screenshot_2020-10-04 Tower UpdateContainer.png

    Screenshot_2020-10-04 pfSense local lan - Firewall NAT Port Forward.pngScreenshot_2020-10-04 pfSense local lan - Diagnostics Test Port(1).pngScreenshot_2020-10-04 Open Port Check Tool - Test Port Forwarding on Your Router.pngScreenshot_2020-10-04 pfSense local lan - Diagnostics Test Port(2).pngScreenshot_2020-10-04 pfSense local lan - Diagnostics Test Port.pngScreenshot_2020-10-04 Open Port Check Tool - Test Port Forwarding on Your Router(1).png

     

    output_log.txt

  2. 1 hour ago, binhex said:

    lan network is invalid, from your log:-

     

    
    2020-08-31 22:36:47.204123 [info] LAN_NETWORK defined as '192.168.0.1/24'

    see Q4 from the following link for how to calculate it correctly:-

    https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

    Thank you, of course it worked. I combed that log for about 3 hours trying to see something that would flag the issue. What made you see what the problem was?

     

    Like I said I was pretty annoyed I couldn't fix it myself, even more annoyed now it turns out the answer is in the FAQ..

  3. I hate that I can't get this working myself. I've combed the FAQ and can't find anything in this thread that seems to match what's going on.

     

    I've had this docker working before, but am only now trying to swap over completely from qbittorrent. I pulled it again and can't seem to get the webui to load.

    Tried deleting all the old config and starting again with no luck. Can't seem to see any significant errors in the supervisord log.

     

    When I try to go into the web ui it times out persistently. Any thoughts?

     

     

    supervisord.log

  4. 12 hours ago, testdasi said:

    A "dotnet" process was killed due to OOM which I think is used by qbittorrent.

    Could be memory leak or could just be naturally out of memory error as you only have 8GB of RAM.

     

    You can try restricting memory usage of some dockers (edit the docker, Advanced View and use --memory=# parameter in Extra Parameters box e.g. --memory=1G to limit memory usage to 1G) and see if it improves things.

    Thanks for the reply. I've limited the memory usage to 3g just to stop it if there's a memory leak. It felt somewhat like a memory leak. It seems odd that I would go from 50% average utilisation to 100% with no significant changes from one day to the next.

     

    I guess if it stops happening after this then I'll look at swapping to rutorrent or something. Cheers for the help.

  5. Fix Common Problems recommended I post my log to the forums.

     

    I've had this server running for about a year now, never got over 50% memory usage. Occasionally CPU usage got up towards 100% but only ever in spikes.

     

    Today I've had an alert twice to say my qbittorrent is down.. once when I woke up. I couldn't access the docker image (didn't think to check any others) and after unraid took too long to load the docker page to restart the docker I just hit restart on the server. Now tonight I've noticed qbittorrent webui wasn't loadable - had a look inside unraid to see CPU and RAM usage at 100%.

     

    I fixed this by stopping all of my docker containers and starting them one by one, leaving the uneccessary ones not running. Seems to be running normally again. Any ideas what caused this?

     

    I'm running unraid Version: 6.8.3

     

     

    tower-diagnostics-20200729-1847.zip

  6. Hey all,

    I'm cleaning up my downloads folder to make a bit more space while I wait for my next drive to arrive.

     

    I want to check that my hardlinks are working correctly and I'm not just duplicating the files after sonarr/radarr imports them. Is there a way to batch audit ~600 files to make sure they are hardlinked and not taking up twice the space on the drive?


    Cheers,

    Tuna.

  7. Hey all,

    What solutions are people using for torrent queueing?

     

    I'm looking to swap from qbittorrent and I was surprised to find this wasn't a feature in rtorrent.

     

    I've noted that pyrocore is included in the container, and https://pyrocore.readthedocs.io/en/latest/advanced.html?highlight=dry_run#rtorrent-queue-manager suggests this implements the functionality I'm describing (i.e. limiting max simultaneous downloads to <4 or whatever, while allowing a larger number of active torrents to seed). I've changed

     job.queue.active  = True

    however, with

    job.queue.downloading_max   = 8

    and rtorrent is still trying to download 50 torrents at once.

     

    Am I doing something wrong?

  8. 1 hour ago, tuna83 said:

     

     

    I'd really like to get qbittorrent working, as I find it the most user friendly client!

     

     

     

    Fixed! I had the wrong subnet in the docker settings.

     

    entered 192.168.0.1 instead of 192.168.0.0

     

    Interestingly, managed to typo that a few times since I think I reinstalled the docker image 3 times.

  9. I'm having trouble getting sonarr/radarr to talk to qBitTorrent. 

    I've done a lot of sleuthing, and after following Radarr's error of 

    19-7-14 16:27:01.9|Warn|HttpClient|HTTP Error - Res: [POST] http://192.168.0.101:8080/login: 503.ServiceUnavailable
    19-7-14 16:27:01.9|Error|QBittorrent|Failed to connect to qBittorrent, please check your settings.
    
    [v0.2.0.1358] NzbDrone.Core.Download.Clients.DownloadClientException: Failed to connect to qBittorrent, please check your settings. ---> NzbDrone.Common.Http.HttpException: HTTP request failed: [503:ServiceUnavailable] [POST] at [http://192.168.0.101:8080/login]
      at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00131] in C:\projects\radarr-usby1\src\NzbDrone.Common\Http\HttpClient.cs:93 
      at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxy.AuthenticateClient (NzbDrone.Common.Http.HttpRequestBuilder requestBuilder, NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings, System.Boolean reauthenticate) [0x000a4] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrentProxy.cs:276 
       --- End of inner exception stack trace ---
      at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxy.AuthenticateClient (NzbDrone.Common.Http.HttpRequestBuilder requestBuilder, NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings, System.Boolean reauthenticate) [0x000e5] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrentProxy.cs:286 
      at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxy.ProcessRequest (NzbDrone.Common.Http.HttpRequestBuilder requestBuilder, NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings) [0x00000] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrentProxy.cs:217 
      at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxy.ProcessRequest[TResult] (NzbDrone.Common.Http.HttpRequestBuilder requestBuilder, NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings) [0x00000] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrentProxy.cs:210 
      at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentProxy.GetVersion (NzbDrone.Core.Download.Clients.QBittorrent.QBittorrentSettings settings) [0x00012] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrentProxy.cs:48 
      at NzbDrone.Core.Download.Clients.QBittorrent.QBittorrent.TestConnection () [0x00000] in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\QBittorrent\QBittorrent.cs:214 

    I found a corresponding error in qBitTorrents logs

    (W) 2019-07-14T20:40:40 -  is not a valid IP address and was rejected while applying the list of banned addresses.
    (N) 2019-07-14T20:40:40 - Web UI: Now listening on IP: *, port: 8080

    Google really didn't bring up much. I suspect most people enable localhost authentication and ignore authentication processes entirely, but I can't get that to work when entering my subnets for the host PC/docker image.

     

    I have no banned addresses entered - this is a clean image of qbit with no settings changed. I tried to enter some with no luck as well.

     

    The only troubleshooting I've really found on this issue is here: https://www.reddit.com/r/qBittorrent/comments/9oej06/is_not_a_valid_ip_address_and_was_rejected_while/

     

     

    The solution

    Quote

    I just found the answer.

    In the Options > WebUI set the IP address to the real address of the server.The problem is that maybe there is a check there for the IP and it drops an exception

     

    Doesn't work either, as changing the IP address to anything else results in being unable to connect to the webui.

     

    I'd really like to get qbittorrent working, as I find it the most user friendly client!

     

     

    Untitled.png

  10. Problem: default username and password ("admin" ; "adminadmin") not working on the qbittorrent webui

     

    Solution: https://github.com/qbittorrent/qBittorrent/wiki/Web-UI-password-locked-on-qBittorrent-NO-X-(qbittorrent-nox)

     

    notably: 

    Quote

    If you are still unable to login check if your antivirus is not blocking sending password via unencrypted connection (http). Bitdefender seems to do it by default, you need to whitelist qbittorrent server url

     

    Bitdefender was blocking me. I tried using a firefox docker through my unraid server and it worked flawlessly.

     

    Hope it helps others having the same problem.