"502 Bad Gateway" when running duck.sh from crontab #271
Description
I noticed that when I run IOTstack/duck/duck.sh in crontab, it often (not always) produces the following error in /var/log/duck.log:
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>
By accident, I noticed also that this doesn't happen if I add a five second delay before the curl command. Have others duckdns users experienced this?
Sounds like this has to be a general issue with Linux networking or cron, but I did a fair bit of searching and didn't find anything. I can create a pull request that adds the five second delay, if I'm not the only one experiencing this. Of course it would be nice to also understand what's causing the problem.
I'm running IOTstack on Raspberry Pi OS.