binarymelon

Members
  • Posts

    25
  • Joined

  • Last visited

Posts posted by binarymelon

  1. I'm wondering if someone could help me with the nut container.  I'm having an issue when trying to run the organize API.  For some reason I end up with many kworker processes completely pegging all my CPU cores at 100%.  I'm not sure what the container would be doing to cause this and I'm not sure what I can do to mitigate it.

  2. I've found I need to tunnel to my unraid server because claiming won't work unless it's accessed on `localhost`.  Not sure if claim codes are required using this process, but if not they've never really worked for me.

     

    ssh <user>@<your_server_ip> -L <your_plex_web_port_or_probably_whatever_port_you_feel_like>:<your_server_ip>:<your_plex_port>

     Then you should be able to navigate to http://localhost:<your_plex_web_port_or_probably_whatever_port_you_feel_like>/web/index.html#!/

     

  3. On 10/1/2021 at 8:23 AM, frodr said:

    I am running binhex-nzbget thru binhex-delugevpn. Up till yesterday no problem, then this error message in binhex-nzbget:

     

    - TLS certificate verification failed for news.eweka.nl: certificate has expired. For more info visit http://nzbget.net/certificate-verification

     

    I downloaded a new conf file from PIA, no change. Before I start the Self signed certificate process, is there another way to fix this?

     

    Most happy for any help.

     

     

    Im experiencing a similar problem with sonarr and radarr.  We’re you able to find a solution.

  4. Just wondering if anyone has any suggestions.  I'm having some issues using the shawly build.  I'm able to run it and connect to it, but no directories or files seem to be visible from multiman.  When I browse to the net0 host the directory is empty.  However when I try and create a directory it does get created on the server, but is still not visible from multiman.

  5. I'm trying to switch over to wireguard, but it seems like I can't connect to the webui while I'm connected to my LAN through a VPN (wireguard to unraid, or l2tp to my gateway).  Verified that the UI can be hit from LAN and from unraid server.  Is this a limitation of wireguard?

  6. On 5/23/2020 at 2:17 PM, IKWeb said:

    Good evening all - When I login to my Plex Web portal - It shows I am running version 1.18, but it tells me 1.19 is out. I cant see anywhere on the docker tab to update this. 

     

    How is an update handeled? Via the plex website it tells me to update manually. 

     

    TIA 

    There should be a 'Check for Updates' button on the docker tab.  It will check and flag any containers that have updates.  After that you can just click 'apply update'.

     

    Does anyone know how often the docker images are updated.  Feature in the latest beta sounds pretty interesting ('Intro Detection') and I'd like to give it a test.

  7. Ok, it seems to be working as expected now.  I have another issue that's tangentially related.  I'm also trying to setup a container (nginx) that has both br0 and bridge networks.  It looks like there used to be a workaround that allowed this, that has since been "fixed".  I'd like to be able to create custom dns entries in pi-hole that point to nginx that proxy to other containers on the bridge network.  Here's an old thread with someone who was looking for a similar solution.

     

     

  8. I'm having a weird (to me at least) issue where I'm getting two devices registered with the same IP on my router (Unifi USG 3) after creating a container using the br0 network to assign it an IP on my LAN.

     

    After creating the container I have two devices with my server IP and 1 device with the docker IP.  1 of the duplicate IP devices corresponds with the br0 device on the server and the other with a shim-br0 device.  Is there anyway I can resolve this?  My ESET security software is getting duplicate IPs and ARP cache poisoning attacks warnings as a result.

    data-raven-diagnostics-20200423-1553.zip

  9. 22 hours ago, Squid said:

    Only solution is to map say /mnt/user to /mnt/user and have both downloads directory and the destination to be referencing /mnt/user/whatever within sonarr.  Also make the same change to your download client

    Hmmm, this didn't actually seem to work.  My client has read only set to false.  I'm not really sure what else to do.