On a configuration with multiple workers and a separate proxy server (but not using docker swarm), I find that mup proxy logs-le incorrectly checks mup-nginx-proxy-letsencrypt on individual containers instead of checking the proxy host:
$ mup proxy logs-le
[worker4.subdomain.subdomain.domain]Error: No such container: mup-nginx-proxy-letsencrypt
[worker2.subdomain.subdomain.domain]Error: No such container: mup-nginx-proxy-letsencrypt
[worker1.subdomain.subdomain.domain]Error: No such container: mup-nginx-proxy-letsencrypt
[worker3.subdomain.subdomain.domain]Error: No such container: mup-nginx-proxy-letsencrypt
mup proxy logs behaves correctly.
Incidentally, mup status also reports "Stopped", "Created at undefined", "Restarted undefined times", and "Available in app's docker container: false". Presumably because I'm not using a docker swarm.
On a configuration with multiple workers and a separate proxy server (but not using docker swarm), I find that
mup proxy logs-le
incorrectly checksmup-nginx-proxy-letsencrypt
on individual containers instead of checking the proxy host:mup proxy logs
behaves correctly.Incidentally,
mup status
also reports "Stopped", "Created at undefined", "Restarted undefined times", and "Available in app's docker container: false". Presumably because I'm not using a docker swarm.Setup
Mup version (
mup --version
): 1.5.2-beta.7Mup config