zaker

I'm seeing that the most recent upgrade sends my docker image into a continual fail and reboot cycle: looking in the logs, I see that: "install: cannot remove '/etc/dnsmasq.d/01-pihole.conf': Read-only file system" the full logs: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole [i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! install: cannot remove '/etc/dnsmasq.d/01-pihole.conf': Read-only file system [i] Installing /etc/dnsmasq.d/01-pihole.conf...[cont-init.d] 20-start.sh: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

Ain't nobody got time to troll thru 228! pages of messages to figure out how to use swag with zerossl on unraid. Looks like linuxserver.io even spends precious little describing what is needed for zerossl. I did find that the github link for docker-swag has a little info though!. There has got to be a better way to support it than this forum.

The idea is to provide a means to monitor one's network. I hate it when you're in a remote desktop connection, zoom meeting or webex or slack, and your session drops or blips for no good reason, but its brief enough that by the time you're ready to investigate, it's back. Is it wireless? Is it my ISP? My router? whodoneit? Well, now we can monitor what we want, revisit the results, and make a plan. zachrybaker/NetConnMon-Docker-Unraid: Storage for an unraid configuration for NetConnMon (github.com)

Hi Everyone. Squid insists we create a support forum for any template we upload. Here it is. I created the template, and I created the software that the template runs.

Sounds like you have the exact same questions I do. The lack of response here should tell us something, I guess. Either @rix is busy, doesn't know, doesn't care. Bummer.

@rix I took a look at the docker file. I think the answer to my question 1 above is the last line of that file tells docker to expose 53, so thats why Unraid shows it exposed. I assume this is not going to get in the way, but also not breaking it technically, if I am set up for port 54? I'm kinda raw on this. 2. Why doesn't path resolution work?

Does anyone know what might cause the two above issues? Have I hit two bugs here?

@rix first off, thanks for your efforts here! I'm trying to get DNSCrypt going. I have a working PiHole setup that I've had working, for quite some time, on port 53. I'm having it look "upstream" to DNSCrypt at port 54. And I'm seeing two issues. 1. The docker config is configured to 54, yet the docker port allocation for DNSCrypt still says 53. See below. My dnscrypt-proxy.toml file is configured for 54: listen_addresses = ['127.0.0.1:54'] 2. At run time it loads my toml file, and it seems content with it, except that if I try to point it to a blacklist file in my configuration folder (see docker config) which is definitely there, it fails. The comment says it is relative to the same directory as the toml file, so I would expect this to just work. If I remove this and my cloaking file path reference altogether (effectively negating most the point of my use of DNSCrypt), it boots just fine. ## Path to the file of blocking rules (absolute, or relative to the same directory as the config file) #fails: blacklist_file = 'dnscrypt-blacklist-domains.txt' # also fails: blacklist_file = './dnscrypt-blacklist-domains.txt' Thoughts?

yes, if I can watch the splash screen not progress, then I have logged in. Yes version 4.3.0. Yes that splash screen just sits there indefinately. I don't see the "can't connect to engine" message.

I'm seeing that the the crashplan desktop app is not ever finishing the desktop app load. It isn't the "cannot connect to engine" error - I can see that my machines are able to back up to it - it just never finishes loading the desktop app. I also saw this happening on a second unraid setup today. Both are the unraid 6 with docker and the desktop image. Both were working fine. Both aren't working now (never gets past loading screen). I was hopeing to configure the servers to back up to each other (you know, off site backup) and without this working, I guess I'm stuck. Any insights appreciated.