strike

No, random is fine

PIA users get automatic port forwarding in this container. All you need to do is enable strict port forwarding in the template and connect to a supported endpoint, that's it. You can also check the log for the incoming port to know it's working.

Which provider do you use? Also, From the FAQ:

Nobody can help you without a log, please follow this procedure: https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

Sure, go ahead

Just remember if you're using some of @binhex other containers like radarr etc, you'll have to do the same change in the volume mappings that you did with deluge. All of @binhex containers use /data as default, so if you don't change the mappings you'll have issues.

What @wgstarks said. What you did was change the container path to /downloads but forgot to change the description so if still said /data

@BennyD You need to understand volume mappings :https://wiki.unraid.net/What_are_the_host_volume_paths_and_the_container_paths

Actually it should be /downloads/incomplete and /downloads/complete

@BennyD From your docker run command post further up your mappings are: '/mnt/user/Downloads/':'/downloads Have you changed this after you posted? please post a new docker run command and a screenshot of your Downloads settings in deluge. Be sure to redact username/password from the ducker run command.

Yes, either you have put in the wrong username/password or it contains special characters which can be problematic.

1. The Netherlands doesn't support port forwarding anymore, switch to another supported endpoint. 2. Check your credentials, the ones you put in are failing. Please use only 0-9,a-z,A-Z characters. From your log:

Thanks! I believe I tried this but it didn't work, can't remember what went wrong though. I'll try it again when I have time.

Any thoughts/ideas regarding this?

Well, I'm creating a jail for repeat offenders and want to have logs for a whole year. So I want to change the rotation to monthly and have it delete any logs older than 13 months. Right now the settings are weekly rotation and I only have logs for 7 weeks.

If I want to make changes to /etc/logrotate.d/fail2ban can I map that file to /config so it doesn't get overwritten on restart? I tried to add a volume mapping but I think I messed it up.. I also need to create a file in /etc/fail2ban but I think that folder is already mapped to /config so I should be able to just create the file in /config/fail2ban/ right? I've never really made any changes to files that are not mapped in the appdata dir in any containers before so I'm a bit lost here.

Sure, if you're using LSIO's let's encrypt container which also has nginx you could just reverse proxy emby. All you need is either an own domain name or a free dynamic DNS service like duckdns. It's pretty easy to set up. Or you can also check out the new container by @Djoss nginx proxy manager which is supposed to be even easier to set up. If you're not comfortable with reverse proxy there is a way to set up just SSL with your LE certificate, but I couldn't tell you how to do it. I know I've seen it somewhere on google though.

Hmm.. I still can't see anything wrong with that. No errors in the log either? It's a long shot, but the only thing I can think of is to remove the comment before geoip_country /config/geoip/GeoIPv6.dat; in your nginx.conf, restart the container and test again. It says in the guide you should put the geo ip part right after http { But then again I can't see why comments should affect that either, as I said a long shot. If all else fail you can try to put it in your proxy conf files instead of the default site config and see if that makes a difference.

Got it, thanks.

Anyone using ldap authentication here? Are there any security benefits from using ldap auth vs basic auth?

Since you started from scratch, please post your nginx.conf and your default site config again.

How are you testing to check if you get blocked or not? Remember you told it to ignore your LAN IP so you must test from outside your LAN. I can't see any obvious reason why it won't work.

Try to move the geoIP part away from your main server block to after the location ~ \.php$ part in your default site config so it looks like this: Location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; include /etc/nginx/fastcgi_params; } # LOCAL IP ALLOW GEO BLOCK if ($lan-ip = yes) { set $allowed_country yes; } # COUNTRY GEO BLOCK if ($allowed_country = no) { return 403; } Edit: And remember to restart the container

You're probably missing something in your site config like the include syntax. Anyways, everything you want to know is in here: https://technicalramblings.com/blog/banning-with-http-auth-and-fail2ban/ He also has a guide on how to use geo IP database to block IP's based on contries which I think you should check out.

I don't use sonarr, but in radarr you have to set the "base URL", I think you have to do the same in sonarr or else you'll be stuck at the loading screen.