You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description: If the web proxy takes long to start (e.g. on a Pi) or fails to start initially and manual admin intervention is required (also on a Pi if it is really overloaded with I/O on a slow SD card), the initial challenge will fail because the web server is offline.
The container then exits and restarts after an hour, but anacron will only re-run the tasks the next day as it still has spool files.
Workaround: docker exec -it snikket-certs rm /var/spool/anacron/cron.daily && docker restart snikket-certs to immediately restart the challenge
The text was updated successfully, but these errors were encountered:
Problem description: If the web proxy takes long to start (e.g. on a Pi) or fails to start initially and manual admin intervention is required (also on a Pi if it is really overloaded with I/O on a slow SD card), the initial challenge will fail because the web server is offline.
The container then exits and restarts after an hour, but anacron will only re-run the tasks the next day as it still has spool files.
Workaround:
docker exec -it snikket-certs rm /var/spool/anacron/cron.daily && docker restart snikket-certs
to immediately restart the challengeThe text was updated successfully, but these errors were encountered: