LetsEncrypt proxy companion ecosystem should be refreshed

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 is a legacy registry. Switch to the new registry for uptodate images: nginxproxy/acme-companion

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:

Info: running acme-companion version v2.5.0-6-gc442dcf
...
Error: can't get nginx-proxy container ID !
Check that you are doing one of the following :
    - Use the --volumes-from option to mount volumes from the nginx-proxy container.
    - Set the NGINX_PROXY_CONTAINER env var on the letsencrypt-companion
    - Set the NGINX_PROXY_CONTAINER env var on the letsencrypt-companion container to the name of the nginx-proxy container.
...
register.freezingsaddles.org: Invalid status. Verification error details: 54.84.77.223: Invalid response from http://register.freezingsaddles.org/.well-known/acme-challenge/B4rooUk2om23AGQf81PwR-ExmU7dpWgAFiEMScd4xA0: 500

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.

freezingsaddles / freezing-compose

LetsEncrypt proxy companion ecosystem should be refreshed #32