Hi @jjmata, thanks for the reply. I just attempted this by re-running docker stack deploy, and by docker service rm [ the service that has the cert label ] then re-deploying, to no avail.
I actually did nothing special the first time around (a simple rm followed by a new deploy did it for me I believe) but it since has stopped working. I’ve resorted to creating the 2 listeners that fail consistently (ports 80 and 443) by hand, and now watch the Github issue where this is being tracked:
@jjmata that thread was actually super helpful. Turns out I had the labels key at the wrong level in docker-compose (it wasn’t under deploy). I moved it and the cert attached first time. I’ll follow that bug in case there are further issues, though.