qaz

Breaking change: Due to the security reason, the “Console” feature is now disabled by default. If you need this feature and understand the risk, you can enable it via the environment variable DOCKGE_ENABLE_CONSOLE=true.

Good that they made a decision, the old security features restricting which commands you could run were awful and could be bypassed by accident. You could run ALLOWED_COMMAMD; RESTRICTED_COMMAND and it would just do it.

I fixed DNS

(My DNS queries were blocked by my ISP’s modem, I flashed OpenWRT on an old WiFi Repeater, and set up a DoH proxy)

Thanks for the advice. I also use a cheap domain with a wildcard, but use nginx instead. I just tried using Adguard and although it’s fascinating to see the insights of all the DNS requests, it didn’t really help fix the issue. However, since using DoH with Cloudflare in combination with setting it to the specific IP instead of my local device name and have 100% uptime now (since the last 10 minutes that is).

I’m using a public DNS record that points to a local device.

*.example.org → example.org
example.org → device_name.lan

Uptime Kuma seems to use nscd for caching internally and the default system DNS resolver. I’ve added a custom DNS resolvers to Uptime Kuma, and apparently it can get the records from Cloudflare (1.1.1.1) but it can’t get it from the OpenWRT router (192.168.1.1). 🤔

I’ve enabled a proxy on the router to force the use of DoH, maybe that will help if the ISP’s modem is at fault.

Since the records have TTL of 5 minutes wouldn’t dnsmasq have to reach to upstream DNS servers every 5 minutes?

If you self-host your own instance, make sure to disable image hosting / caching. I’ve had to DM a lot of people to inform them of “problematic” images hosted on their instance.