WannabeMKII

I've just run this on my install with the following output; docker exec -it pihole apt-get update docker exec -it pihole apt-get --reinstall install iptables docker exec -it pihole apt-get install iptables-persistent docker exec -it pihole iptables -A INPUT -p tcp --destination-port 443 -j REJECT --reject-with tcp-reset docker exec -it pihole iptables -A INPUT -p udp --destination-port 80 -j REJECT --reject-with icmp-port-unreachable docker exec -it pihole iptables -A INPUT -p udp --destination-port 443 -j REJECT --reject-with icmp-port-unreachable docker exec -it pihole ip6tables -A INPUT -p tcp --destination-port 443 -j REJECT --reject-with tcp-reset docker exec -it pihole ip6tables -A INPUT -p udp --destination-port 80 -j REJECT --reject-with icmp6-port-unreachable docker exec -it pihole ip6tables -A INPUT -p udp --destination-port 443 -j REJECT --reject-with icmp6-port-unreachable docker exec -it pihole iptables-save > /etc/iptables/rules.v4 Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB] Get:2 http://security.debian.org jessie/updates/main amd64 Packages [608 kB] Ign http://deb.debian.org jessie InRelease Get:3 http://deb.debian.org jessie-updates InRelease [145 kB] Get:4 http://deb.debian.org jessie Release.gpg [2434 B] Get:5 http://deb.debian.org jessie Release [148 kB] Get:6 http://deb.debian.org jessie-updates/main amd64 Packages [23.1 kB] Get:7 http://deb.debian.org jessie/main amd64 Packages [9064 kB] Fetched 10.1 MB in 3s (2824 kB/s) Reading package lists... Done Not sure if there's anywhere in particular I can look to check? But I'll keep an eye on things to see how things run... Thanks @spants

I use that at the moment for a general overview, but I was hoping for a bit more detail of the specifics if I can?

Quite a while ago, Community Applications used to have a button or option to see how much RAM and CPU each docker was using. It disappeared quite a while ago, but I miss it. Is the setting still there somewhere, or is there an alternative that gives this info?

Awesome, thanks spants and hope you had a great time travelling!!!

To be honest, I wouldn't even know where to begin in terms of adding the info manually, especially if there's a risk of it being wiped after an update. @spants, is it possible to have the required settings baked into the container for a future release? I'd love to use this, as the www is getting more and more littered with ads!

Ah ha, 'DNS resolution not currently available' resolved thanks to your link, appreciated! As for the second section, that's gone straight over my head Is this something I can do manually, or is this something that can be added to the docker?

Great. I'll keep an eye on things. Thanks for your help!

This is what I'm seeing...?

Thanks for the pointer. I've done that, but I don't seem to see anything relating to 'orphaned containers'? Is there somewhere in particular I should be looking?

I've had 2 docker images update today and each time, when updating the docker images, it fails and removes the container totally. I then go into apps, install the app again and it works perfectly, retaining all the settings? I've checked the logs and this is the only warning I can see, but not sure what to do? Feb 6 11:01:00 TechNAS [26693]: The command failed. Error: sh: /usr/local/emhttp/usr/bin/docker: No such file or directory<br>

No worries, I'll leave it as it is and save my money. It's sitting at 44% on the dashboard, so assume that's OK. Thanks again!

Thanks for the info, appreciate how caching works, just wondering if I'd really benefit from more RAM or not. It's been fine the last year or so, just wondered if it was a relatively cheap upgrade to get better performance or not...

Here's a screenshot of my RAM. We're streaming a film on the network at the moment. The used is pretty static, but the cached does drop down to about 60% or so when 'resting'...

Found the issue and it was really subtle. Within nzbhydra, the URL base is actually greyed as an example and not actually completed. I typed in "/nzbhydra" and it's now working perfectly! So everything is now back to 100% working order, thanks again for the pointers everyone!

I'm running my unraid on an N54L with 4GB RAM. I currently have 6 docker containers running, no VM's and it serves all my files, media, backups etc. I wondered if I'd see any benefit of doubling the RAM to 8GB?

Sorry, got excited that things are almost 100%. Attached are images and the LE setup; location /nzbhydra { include /config/nginx/proxy.conf; proxy_pass http://10.0.0.124:5075/nzbhydra; }

I've tried using Pi-Hole three times. Once on 6.3.5, once on 6.4 and again on 6.4, but with it's own IP. The problem I'm having is that 75% of time, everything is fine, but every now and again, pages just don't load. They hang and hang and refreshing the page 2 or 3 times then causes it to load? Any ideas? The only other thing I've noticed is that I get the following on startup and when updating the lists; [✗] DNS resolution is currently unavailable I'm not sure why?

This is working great, but now I've LetsEncrypt back up and running, when accessing, it prompts for my username and password, but not actually loads? It appears to access my login credentials, but the page doesn't render anything? Any ideas?

Ah ha, adding "tls-sni" = "true" has got me back up and running! Port 80 is still appearing as closed though? Now just to get nzbhydra2 actually loading properly. Superb news though and really appreciate the constant help from everyone, absolutely legendary!

OK. I'll wait for the new version to be available, then nuke everything and start again. Just out of interest, what's the ETA on the new version? Are we talking hours, days...?

Should I just nuke my LE container, appdata etc and start again?

OK. I had to delete that section and re-add it and now done; root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "EMAIL"="*****@*****.***" -e "URL"="*****.***" -e "SUBDOMAINS"="*****" -e "ONLY_SUBDOMAINS"="true" -e "DHLEVEL"="2048" -e "HTTPVAL"="true" -e "PUID"="99" -e "PGID"="100" -p 444:443/tcp -p 81:80/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt 2e883074e4fa57872dcfe4dbe866e245bdb871a60f8010e34cdf2bf7ca3d997c The command finished successfully! I've also attached the port forwarding. LE logs; [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Backwards compatibility check. . . Still using tls-sni. Please set the VALIDATION parameter in the future 2048 bit DH parameters present SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d *****.*****.*** E-mail address entered: *****.*****.*** Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container Hopefully this show's everything...?

Ah got you, sorry. After changing the port, I get the following; root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "EMAIL"="*****@*****.***" -e "URL"="*****.***" -e "SUBDOMAINS"="*****" -e "ONLY_SUBDOMAINS"="true" -e "DHLEVEL"="2048" -e "HTTPVAL"="true" -e "PUID"="99" -e "PGID"="100" -p 80:81/tcp -p 444:443/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt 1d79d9f9dc01fd82456b2131a0311e4d33eb32a8ed50b55b026349ea5bde2033 /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint letsencrypt (176839ccbca9b1aa09ea179adc960f4d4b1887c58ead94c06b6ef5bb2006a44e): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use. The command failed. I guessing this is because of it being the same port and IP of unraid?

We've tried all variations to get it to work and we're back to sharing the IP with unraid.

No space anywhere on 'true'. Here's the run command; root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "EMAIL"="*****@*****.***" -e "URL"="*****.***" -e "SUBDOMAINS"="*****" -e "ONLY_SUBDOMAINS"="true" -e "DHLEVEL"="2048" -e "HTTPVAL"="true" -e "PUID"="99" -e "PGID"="100" -p 81:81/tcp -p 444:443/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt 0d992b727e55d3d67b94761e56853cd0ba7df419c3e8050ddb17d8304b908227 The command finished successfully! I mentioned about dnsmadeeasy, as was going to give it a try for you, but guess it's not worth it until this is working.