strike

None. Connect to one of the endpoints that support port forwarding, that's it. And enable strict port forwarding in the container settings

If you drop the .crt and the .pem file in the same dir as the .ovpn file I think you should be good to go You'll find them in the same .zip from PIA. You should also change your password ASAP. Remember to remove it from the log next time Edit: reported your post to remove the logfile

Hmm.. Then I have no clue, can't spot anything obvious in the log either.

You mentioned you're using chrome, do you use an extention or do you use the proxy setting in the OS? If you are using an extention have you tried a diffrent one? I remember a another user having problems with a chrome proxy extention, and IIRC he solved it by using a different extention. Or maybe configure your OS settings to use the proxy. Please also post your entire supervisord.log from you delugevpn appdata folder, maybe we can spot something there. Edit: And yeah, please enable debug logging in the deluge container

Have you tried to nuke your docker image and pull down all the containers again? I Remember having this issue once and I think that solved it for me

In sickrage you must include http:// looking at your SR log it looks like you just have defined 192.168.0.101:8118

First, you need to add a path in you docker template and point it to where your log is. Then you need to add a new jail to ../fail2ban/jail.local and just point the logpath to the path you just created. That’s about it. You might wanna adjust the bantime, findtime and maxretry too. The default bantime is just 10 min which is too low IMO. If you use nginx auth there's already jails in place to monitor your nginx log so you don't need to add that. Edit: I forgot that you'll need to add a filter to ../fail2ban/filter.d Just call it minio.conf or something.This is my filter for my emby server: # Fail2Ban filter for emby # [INCLUDES] # Read common prefixes. If any customizations available -- read them from # common.local before = common.conf [Definition] _daemon = emby-server failregex = Info HttpServer: HTTP Response 401 to <HOST>.*authenticatebyname Info HttpServer: HTTP Response 500 to <HOST>.*mediabrowser/Users/None ignoreregex = # DEV Notes: # # Matching on http 401 with a trailing url including 'authenticatebyname' to catch incorrect passwords # Matching on http 500 with a trailing url including 'mediabrowser/Users/None' to catch incorrect usernames # # Author: [email protected]

Yeah, and also the .crt and .pem files, forgot about those.. I always do since I use AirVPN I only need the .ovpn file.. :P

Just replace the .ovpn file you have in your /config/openvpn folder with one from the zip, I always recommend the Netherlands one. Then restart the container. You shouldn't need to change anything else in the template as of recent updates the container pulls all the needed info from the .ovpn file.

I don't use sonarr, but I had the same problem with radarr the first time I set up this container. Turned out I forgot to set the "URL Base" in the webui settings for radarr.

@krobson17 Or this zip which connects over TCP 443, https://www.privateinternetaccess.com/openvpn/openvpn-ip-tcp.zip if @binhex's zip doesn't do the trick ( it uses TCP 502 rather than 443). But both are definitely worth a try, I found that trying different ports and protocols made a huge difference in speed. Unfortunately, some ISP's applies caps/blocks on some ports so if it works you know why. Edit: Pasted the wrong link, fixed..

Edit ../fail2ban/action.d/iptables-common.conf and comment out the last section so it looks like this: [Init?family=inet6] # Option: blocktype (ipv6) # Note: This is what the action does with rules. This can be any jump target # as per the iptables man page (section 8). Common values are DROP # REJECT, REJECT --reject-with icmp6-port-unreachable # Values: STRING #blocktype = REJECT --reject-with icmp6-port-unreachable # Option: iptables (ipv6) # Notes.: Actual command to be executed, including common to all calls options # Values: STRING #iptables = ip6tables <lockingopt> Restart the container

@krobson17, @wgstarks Regarding the low speed, one thing you can try is to switch to a tcp connection, preferably TCP 443 or 53 if possible. Where I live many ISP's throttle UDP VPN connections, dont ask me why. When I was a PIA member I had to switch to a TCP connection to get the speed I wanted. So try to download a new opvn file which connects over TCP. I don't know if this is possible with PIA now, but it was at least when I was a member. If you can't find a new file ask PIA if they can send one to you if they support it. If not I would switch provider, AirVPN maybe. If you guys have checked your settings and everything is ok then I'm almost certain you're suffering form ISP throttling.

I have tried vyprvpn (many years ago), PIA, Expressvpn and AirVPN. AirVPN is by far the best one of these, IMO anyway. AirVPN lets you mask that you’re using a vpn by connecting over SSH/SSL or even TOR. They also do some kind of sweet routing trick that lets you access certain websites like BBC iplayer form any of their endpoints, not just UK ones. Regarding vyprvpn it might not work with delugevpn:

No vpn providers has magic servers.. To do p2p you MUST have an open incoming port to get decent speed. That is just the way it’s designed. If you guys are using PIA, the only thing you must configure is VPN_PROV = PIA and STRICT_PORT FORWARD = yes. And you must be connected to one of the endpoints that support port forwarding. If you have done that, then this container will take care of the port forwarding for you automagically.

No, parity does not require raid. And unraid is not raid at all. You can have up to two parity drives. If you want to learn more about unraid a good place to start is @gridrunner youtube channel. https://www.youtube.com/channel/UCZDfnUn74N0WeAPvMqTOrtA/videos You can start with this one: You also have the wiki/manual but it's a bit outdated: https://wiki.lime-technology.com/UnRAID_Manual_6 This forum also have massive amounts of information. The unraid community is just awesome! As many have said "came for the software, stayed for the community"

Been a long time since I've configured this (6.1 days), but if you guys read the info on github and the readme located in the plugin folder I'm sure you'll be able to figure it out. I'm using key based login only and it works like a charm. Github: https://github.com/docgyver/unraid-v6-plugins Readme located on your flashdrive in /boot/config/plugins/ssh

Hmm..Then I'm not really sure what the issue is. I can't see anything obvious in the log, better wait for someone else to chime in.

You're supposed to have only one .ovpn file in the openvpn folder, remove the rest. The vpn tunnel is up so if you're not getting to the webui it's maybe because of the extra files you have in the openvpn folder or your LAN_NETWORK is wrong. What is your unraid IP?

Just ignore that warning. Are you able to get to the webui now after making those changes? If not please enable debug logging by changing the DEBUG variable to true. Delete the /config/supervisord.log, start the container and let it run for a few min and post the entire log here. Remove username/pw of course. As for the incoming port you need to check if your provider supports it and do whatever you have to do to open a port. Then add that port in the deluge webui settings not the docker settings. Do not open any ports on your router.

Couple things here. First change VPN_PROV to custom, second remove what you have in VPN_OPTIONS and leave it blank. I haven't tried vyprvpn for a long time so I don't remember if they support port forwarding. But if they don't you might want to change provider as you won't really be able to torrent as torrenting require an open incoming port. If they do support port forwarding you need to use whatever endpoints that support it, I doubt the one you have chosen does.

np One thing I missed when reading the log last time: As stated in the log, if you have special characters in your password this can cause authentication issues.

You have a successful start and are connected to the vpn. One thing tho, you should have only one ovpn file in the openvpn folder. And you must pick one of the endpoints which support port forwarding or else you won't be able to get any decent speed as torrenting require an open incoming port. The Netherlands is a good one, remove all the rest of the opvn files you have in the openvpn folder. If you want to change endpoints later just replace the opvn file with another endpoint and restart the container.

Please enable debug by stopping the container, setting the DEBUG variable to true, delete /config/supervisord.log. start the container and let it run for a few min then post the entire logfile here. Be sure to remove any username/password before you post it.

Remove whatever you have in the VPN_OPTIONS variable. This is for advanced vpn options only, so if you don't know how to use it leave it blank