Open ssanj opened 6 years ago
This seems to be an on-going problem.
The current workaround is to stop and start the containers:
docker-compose down docker-compose up
You may see a HTTP 500 error for a while until the sample container starts.
This makes me think that the certs were already updated but not live somehow (as I didn't see any indication of getting new certs).
Another possible fix would be to rebuild the full stack so we can get the latest versions of the full stack.
The docker-letsencrypt-nginx-proxy-companion has a newer version that has two useful scripts in it:
docker exec nginx-letsencrypt /app/cert_status
docker exec nginx-letsencrypt /app/force_renew
I've updated docker-letsencrypt-nginx-proxy-companion to the latest version but left the rest of the stack as is. If this issue continues I will also update:
This seems to be an on-going problem.
The current workaround is to stop and start the containers:
You may see a HTTP 500 error for a while until the sample container starts.
This makes me think that the certs were already updated but not live somehow (as I didn't see any indication of getting new certs).
Another possible fix would be to rebuild the full stack so we can get the latest versions of the full stack.
The docker-letsencrypt-nginx-proxy-companion has a newer version that has two useful scripts in it:
docker exec nginx-letsencrypt /app/cert_status
docker exec nginx-letsencrypt /app/force_renew