LetsEncrypt proxy companion ecosystem should be refreshed #32
Labels
enhancement
New feature or request
help wanted
Extra attention is needed
infrastructure
Issues requiring changes to cloud, database, or server infrastructure
Milestone
On 2024-11-10 after an update of containers, the LetsEncrypt certificates stopped working. It looks like https://hub.docker.com/r/jrcs/letsencrypt-nginx-proxy-companion/tags now says:
This container version had not been pinned, so it auto-updated to what appears to be a version of nginxproxy/acme-companion. We should probably switch to that one, but if we can squeeze through the 2025 season with the current config, it might be good...
This started running acme-companion instead... logs were similar to the following:
Depending on the version used, the verification error for the
.well-known/acme-challenge/*
file was either a 500 or 404. It wasn't working in any case.This can be tested on a test system on AWS that is spun up temporarily in much the same way we created an alternate web site https://tmp-www.freezingsaddles.org/ during freezingsaddles/freezing-web#280 and #35 - that way we don't have to bring down the site to test.
The text was updated successfully, but these errors were encountered: