My external URL via DuckDNS is hit or miss. If I find I cannot access using the external address, I log in at home using the IP address directly to the device and check the logs to DuckDNS. Nine times out of ten, the external URL then starts to work again. Almost as if the DuckDNS check triggers it to renew, although the logs do not show that.
However, I noticed two things on the log this evening that I haven’t seen anyone else mention (forgive me if I didn’t search hard enough!).
A check this afternoon showed this in the DuckDNS log:
+ Checking domain name(s) of existing cert... unchanged.
+ Checking expire date of existing cert...
+ Valid till Oct 17 19:52:57 2024 GMT (Longer than 30 days). Skipping renew!
[19:00:06] INFO: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>
So I restarted, and all was fine. Then this evening the external URL wasn’t working again, and the log showed this:
+ Checking domain name(s) of existing cert... unchanged.
+ Checking expire date of existing cert...
+ Valid till Oct 17 19:52:57 2024 GMT (Longer than 30 days). Skipping renew!
[21:28:49] WARNING:
[22:23:58] WARNING:
The two WARNING remarks don’t give any other context, and the separate Home Assistant Logger shows nothing in it either.
I cannot see a way to enable better logging to get to the bottom of this particular error.
Has anyone seen a Bad Gateway error in the DuckDNS logs before? Or seen the no-context Warning message?
This is on a Raspberry Pi 4, running Core 2024.8.2, Supervisor 2024.08.0, OS 13.0 and Frontend 20240809.0 and DuckDNS version 1.18.0