MyKroFt

puttygen /boot/config/plugins/ssh/mykroft/.ssh/id_rsa -o /boot/config/plugins/ssh/mykroft/.ssh/id_rsa.ppk getting error: puttygen: error loading `/boot/config/plugins/ssh/mykroft/.ssh/id_rsa': unrecognised key type I did use ssh-keygen -t rsa -f /boot/config/plugins/ssh/<USERNAME>/.ssh/id_rsa to generate key any suggestions?

Aug 10 20:42:25 Tower inotifywait[26383]: Failed to watch /mnt/cache; upper limit on inotify watches reached! Aug 10 20:42:25 Tower inotifywait[26383]: Please increase the amount of inotify watches allowed per user via `/proc/sys/fs/inotify/max_user_watches'. Anyone tell me what that means:? Thanks Myk

from the github page How does AdGuard Home compare to Pi-Hole At this point, AdGuard Home has a lot in common with Pi-Hole. Both block ads and trackers using "DNS sinkholing" method, and both allow customizing what's blocked. We're not going to stop here. DNS sinkholing is not a bad starting point, but this is just the beginning. AdGuard Home provides a lot of features out-of-the-box with no need to install and configure additional software. We want it to be simple to the point when even casual users can set it up with minimal effort. Disclaimer: some of the listed features can be added to Pi-Hole by installing additional software or by manually using SSH terminal and reconfiguring one of the utilities Pi-Hole consists of. However, in our opinion, this cannot be legitimately counted as a Pi-Hole's feature. FeatureAdGuard HomePi-Hole Blocking ads and trackers✅✅ Customizing blocklists✅✅ Built-in DHCP server✅✅ HTTPS for the Admin interface✅Kind of, but you'll need to manually configure lighthttp Encrypted DNS upstream servers (DNS-over-HTTPS, DNS-over-TLS, DNSCrypt)✅❌ (requires additional software) Cross-platform✅❌ (not natively, only via Docker) Running as a DNS-over-HTTPS or DNS-over-TLS server✅❌ (requires additional software) Blocking phishing and malware domains✅❌ Parental control (blocking adult domains)✅❌ Force Safe search on search engines✅❌ Per-client (device) configuration✅❌ Access settings (choose who can use AGH DNS)✅❌

For some reason all of a sudden my Medusa will not completly start up Log shows the following 2019-06-16 01:15:32 INFO MAIN :: [0c0a735] Broken providers found: [u'torrent9', u'newpct', u'tntvillage'] 2019-06-16 01:15:41 INFO MAIN :: [0c0a735] 12345: Unable to find the show in the database 2019-06-16 01:15:41 INFO MAIN :: [0c0a735] 320558: Unable to find IMDb info in the database: Marvel's Inhumans 2019-06-16 01:15:41 INFO MAIN :: [0c0a735] Starting Medusa [master] using u'/config/config.ini' 2019-06-16 01:15:41 INFO TORNADO :: [0c0a735] Starting Medusa on http://0.0.0.0:8081/ 2019-06-16 01:15:41 INFO MAIN :: [0c0a735] Updating exception_cache and exception_season_cache 2019-06-16 01:15:41 INFO MAIN :: [0c0a735] Finished processing 3101 scene exceptions. 2019-06-16 01:15:41 INFO MAIN :: [0c0a735] Building internal name cache for all shows 2019-06-16 01:15:42 INFO CHECKVERSION :: [0c0a735] Checking for updates using Docker Updater and it sits on the CHECKVERSION line forever with never completly loading up any suggestions on what to look for? Thanks

hm... dosent rutorrent have a move when completed plugin installed already?

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; } }