strike

Members
  • Posts

    771
  • Joined

  • Last visited

Everything posted by strike

  1. So after almost 10 years using medusa I switched over to sonarr as medusa was becoming painfully slow. 1 thing I'm missing tho is what's called scene exceptions in medusa. This is a feature where you can add another name to the show than what it's called when your're pulling it from tvdb or whatever indexer. Sometimes the show is released with another name, as an example I'm using the the show "The Idol 2023". On the tracker I'm using the show is released as "The Idol US" or "The Idol". But since the show is called The Idol 2023 in sonarr it doesn't find any episodes. So how do I solve this in sonarr?
  2. That might be, but something could have changed with your vpn provider so the port isn't open anymore.
  3. From your log. Check the faq and you'll find the answer. I would link it, but I'm on my phone so I don't have it handy.
  4. The number one reason for low speed is not having an open incoming port. Have you set that up with your vpn provider and put that port in the deluge settings?
  5. No, nothing special. I've just tried it for a few min tho. It was as I said useless to me as it doesn't support labels.
  6. It is, but it doesn't support labels yet. So it's pretty much useless if you're using automation software like Sonarr/radarr etc.
  7. Follow the instructions in the jacket webui. If you have problems maybe check the support thread for jackett.
  8. Check the FAQ, everything is in there, specifically from Q24 and down. https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  9. You're right, change LAN_NETWORK to 192.168.3.0/24
  10. That depends, winrar in windows does not copy symlinks for example. And I don't know if it preserves permissions either. Best way to do it is via the CLI. It's super simple and faster.
  11. Haha I do feel a bit warmer and fuzzier now that you mention it. But this is the container I trust the most so I wasn't really worried about that. If it weren't for all my other containers running on br0 with a separate IP I would run this container in bridge so I could reverse proxy it. But I can live with just the thin client, it works well.
  12. Yeah, I like to have most of my containers on a separate IP as well, for security reasons for the most part. As they are then isolated from the host. So I'm using the thin client for deluge. The only thing I miss that I can't get from the thin client, is to set up a reverse proxy.
  13. Good to know, I'll be watching this issue. If they all have airvpn I might know what the solution is. @Lamkam is using airvpn I can see from the little log snippet. I'll ask on the github issue if they can confirm which provider they're using.
  14. Last image is working fine here. Do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md
  15. https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=1223362
  16. Ok, Yeah a lot of users had permission issues when updating to 6.11 due to not using the correct setup. If you have the arrs running on another uid/gid other then 99/100 you need to change it back to the standard 99/100. And make sure the right permission are set in the settings of the arrs. After doing that you might need to run the new (docker safe) perms script found under tools in the unraid webui on you shares to fix permission issues.
  17. You mean you can't get to the webui of the arrs? Has it been a while since you updated delugevpn? There was some changes some time ago when routing other apps through a vpn app. Do you have your input and output ports setup according to the faq Q25 and Q27? https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  18. Do you know how to use the command line? Or Midnight Commander? Just ssh into your server or click the terminal in the unraid webui. type mc and hit enter. Navigate to the appdata folder and delete it from there.
  19. Remove "ncp-disable" from your .ovpn file and retart the container.
  20. This seems to be your issue: 2023-02-13 08:56:48 VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=US, ST=VPN, L=VPN, O=VPN, OU=VPN, CN=VPN, name=VPN, emailAddress=VPN, serial=1 2023-02-13 08:56:48 OpenSSL: error:0A000086:SSL routines::certificate verify failed 2023-02-13 08:56:48,838 DEBG 'start-script' stdout output: 2023-02-13 08:56:48 TLS_ERROR: BIO read tls_read_plaintext error 2023-02-13 08:56:48 TLS Error: TLS object -> incoming plaintext read error 2023-02-13 08:56:48 TLS Error: TLS handshake failed It looks like your vpn provider is issuing a week cert, you need to get a updated one from your vpn provider.
  21. You have redacted too much of the log. What is your LAN_Network set to? What is the IP of your unraid server? And what network type do you have set in the docker template?
  22. Try to delete the perms.txt in your appdata and restart the container. Post a new log if you can't get to the webui.