MyKroFt

does this docker have the tools to setup DOH? Ex: https://docs.pi-hole.net/guides/dns-over-https/ I could add manually, but then changes would be lost anytime the docker container gets updated.... Thanks Myk

you have a path to custom stop/start scripts - am assuming that is a way to only shutdown certain dockers via script. what about a before/after - that can be run and let the backup program manage stopping/starting the dockers itself if I am reading correctly what the custom stop/start are to be used for?

Is there a possibility to add a before/after path to custom script option?

Any consideration on this? Thanks Myk

As always, thanks for your addons, makes management 1000% better..... Request: Backup - detect extra docker networks and backup their info Restore - recreate extra docker networks before restore I had just corrupted my cache drive some how and did a restore (went well) - but some dockers were not working, took me a bit to figure out they were on a custom network for my reverse proxies stuff. Had to manually create network, edit each docker to change to network to something else and back to custom network so it would re save and restart docker to use custom network (just restarting would not make it use custom network). Thanks for the consideration of this request. Myk

ya running pihole and https://192.168.0.104 does not work for me either when no internet hm... stumped

Ya pings just fine. It trys to resolve to my unraid.ner domin name. When I enter 192.168.0.104, it trys to resolve a.domin name and fails It's trying to resolve to an HTTPS maybe that's what's causing it

Why when there is a internet outage you can not access the UI via local lan IP?

Am really trying here :( /banging head on desk changed the offending line to: server_name bitwarden.*; and now I am getting timeouts :( current conf file # make sure that your dns has a cname set for bitwarden server { listen 80; server_name bitwarden.*; return 301 https://$server_name$request_uri; } server { listen 443 ssl http2; server_name bitwarden.*; include /config/nginx/ssl.conf; set $upstream_bitwarden bitwarden; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; location / { proxy_pass http://$upstream_bitwarden:8343; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub { proxy_pass http://$upstream_bitwarden:3012; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://$upstream_bitwarden:8343; } }

this is what I am trying to use already from the blog post, but am getting bad gateway # make sure that your dns has a cname set for bitwarden server { listen 80; server_name bw.*; return 301 https://$server_name$request_uri; } server { listen 443 ssl http2; server_name bitwarden.*; include /config/nginx/ssl.conf; set $upstream_bitwarden bitwarden; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; location / { proxy_pass http://$upstream_bitwarden:8343; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub { proxy_pass http://$upstream_bitwarden:3012; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://$upstream_bitwarden:8343; } }

ok, being dumb here, have searched and tried configs for over 1 hr now... does anyone have a working bitwarden config for subdomain w/docker on a seperate proxeynet my others work just fine, but this one is making me pull out what hair i have left help pls Myk

STarted getting the following error 2 days ago: Mar 11 01:25:08 Tower nginx: 2019/03/11 01:25:08 [error] 17554#17554: OCSP responder timed out (110: Connection timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: 104.80.88.113:80, certificate: "/etc/ssl/certs/unraid_bundle.pem" where should I start to even look? I can not contact it even from a system outside of my local lan......

give Duplicati a serious look. Been using it for about a year. Nice docker avail in the apps tab Myk

nope

current version of unraid (rc2) and docker container, I can only access the unraid base ip, I can no longer access anything else on the local lan because of the missing routing information