Unhealthy proxy container

After adding a new service user for MQTT protocol, the user page was not loading. In this old thread someone had the same problem. After updating my docker pull openremote/manager, I tried to docker-compose up on EXTERNAL_URL. Previously this was working, but now I get ERROR: for proxy Container "xxx" is unhealthy. ERROR: Encountered errors while bringing up the project.

Is there a way to resolve this problem?

Thanks in advance

Please paste the logs for the unhealthy container…we can’t help without that info. If you’re not trying to preserve data then ensure you do a docker volume prune between docker-compose down and docker-compose up.

Sorry didn’t know that you needed the logs. Perhaps it was a more common problem. But herby my logs. I do try to preserve the data that is located in postgresql.

[INFO][2021-11-03 14:18:28] DOMAINNAME: localhost
[INFO][2021-11-03 14:18:28] LOCAL_CERT_FILE:
[INFO][2021-11-03 14:18:28] HAPROXY_CERT_FILE: /opt/selfsigned/localhost.pem
[INFO][2021-11-03 14:18:28] HAPROXY_CONFIG: /etc/haproxy/haproxy.cfg
[INFO][2021-11-03 14:18:28] HAPROXY_CMD: haproxy -f /etc/haproxy/haproxy.cfg  -D                                                                              -p /var/run/haproxy.pid
[INFO][2021-11-03 14:18:28] HAPROXY_USER_PARAMS:
[INFO][2021-11-03 14:18:28] PROXY_LOGLEVEL: notice
[INFO][2021-11-03 14:18:28] LE_CERT_ROOT: /deployment/letsencrypt/live
[INFO][2021-11-03 14:18:28] LE_ARCHIVE_ROOT: /deployment/letsencrypt/archive
[INFO][2021-11-03 14:18:28] LE_RENEWAL_CONFIG_ROOT: /deployment/letsencrypt/rene                                                                             wal
[INFO][2021-11-03 14:18:28] LE_CMD: /usr/bin/certbot certonly --config-dir /depl                                                                             oyment/letsencrypt -w /deployment/acme-webroot
[INFO][2021-11-03 14:18:28] LOGFILE: /var/log/proxy.log
Starting enhanced syslogd: rsyslogd.
[INFO][2021-11-03 14:18:29] Checking HAProxy configuration: /etc/haproxy/haproxy                                                                             .cfg
Configuration file is valid
[info] 306/141829 (49) : [acme] http-01 plugin v0.1.1
Nov  3 14:18:29 localhost haproxy[49]: Proxy http started.
Nov  3 14:18:29 localhost haproxy[49]: Proxy https started.
Nov  3 14:18:29 localhost haproxy[49]: Proxy mqtt started.
Nov  3 14:18:29 localhost haproxy[49]: Proxy manager_backend started.
Nov  3 14:18:29 localhost haproxy[49]: Proxy keycloak_backend started.
Nov  3 14:18:29 localhost haproxy[51]: mqtt/proxy_backend_host changed its IP fr                                                                             om  to 172.18.0.4 by docker_resolver/dns.
Nov  3 14:18:29 localhost haproxy[51]: Server mqtt/proxy_backend_host ('manager'                                                                             ) is UP/READY (resolves again).
Nov  3 14:18:29 localhost haproxy[51]: Server mqtt/proxy_backend_host administra                                                                             tively READY thanks to valid DNS answer.
Nov  3 14:18:29 localhost haproxy[51]: manager_backend/proxy_backend_host change                                                                             d its IP from  to 172.18.0.4 by DNS cache.
Nov  3 14:18:29 localhost haproxy[51]: Server manager_backend/proxy_backend_host                                                                              ('manager') is UP/READY (resolves again).
Nov  3 14:18:29 localhost haproxy[51]: Server manager_backend/proxy_backend_host                                                                              administratively READY thanks to valid DNS answer.
Nov  3 14:18:29 localhost haproxy[51]: keycloak_backend/proxy_backend_host chang                                                                             ed its IP from  to 172.18.0.3 by docker_resolver/dns.
Nov  3 14:18:29 localhost haproxy[51]: Server keycloak_backend/proxy_backend_hos                                                                             t ('keycloak') is UP/READY (resolves again).
Nov  3 14:18:29 localhost haproxy[51]: Server keycloak_backend/proxy_backend_hos                                                                             t administratively READY thanks to valid DNS answer.
[INFO][2021-11-03 14:18:29] HAProxy started with /etc/haproxy/haproxy.cfg config                                                                             , pid 51.HAPROXY_CERT_FILE
[INFO][2021-11-03 14:18:29] Executing cron_auto_renewal_init at Wed, 03 Nov 2021                                                                              14:18:29 +0000
[INFO][2021-11-03 14:18:29] Domain is 'localhost', dummy SSL certificate does no                                                                             t have to be renewed
[INFO][2021-11-03 14:18:29] Monitoring config file /etc/haproxy/haproxy.cfg and                                                                              certs in /deployment/letsencrypt/live for changes...
[INFO][2021-11-03 20:27:35] DOMAINNAME: localhost
[INFO][2021-11-03 20:27:35] LOCAL_CERT_FILE:
[INFO][2021-11-03 20:27:35] HAPROXY_CERT_FILE: /opt/selfsigned/localhost.pem
[INFO][2021-11-03 20:27:35] HAPROXY_CONFIG: /etc/haproxy/haproxy.cfg
[INFO][2021-11-03 20:27:35] HAPROXY_CMD: haproxy -f /etc/haproxy/haproxy.cfg  -D                                                                              -p /var/run/haproxy.pid
[INFO][2021-11-03 20:27:35] HAPROXY_USER_PARAMS:
[INFO][2021-11-03 20:27:35] PROXY_LOGLEVEL: notice
[INFO][2021-11-03 20:27:35] LE_CERT_ROOT: /deployment/letsencrypt/live
[INFO][2021-11-03 20:27:35] LE_ARCHIVE_ROOT: /deployment/letsencrypt/archive
[INFO][2021-11-03 20:27:35] LE_RENEWAL_CONFIG_ROOT: /deployment/letsencrypt/rene                                                                             wal
[INFO][2021-11-03 20:27:35] LE_CMD: /usr/bin/certbot certonly --config-dir /depl                                                                             oyment/letsencrypt -w /deployment/acme-webroot
[INFO][2021-11-03 20:27:35] LOGFILE: /var/log/proxy.log
Starting enhanced syslogd: rsyslogd.
[INFO][2021-11-03 20:27:37] Checking HAProxy configuration: /etc/haproxy/haproxy                                                                             .cfg
Configuration file is valid
[info] 306/202737 (47) : [acme] http-01 plugin v0.1.1
Nov  3 20:27:37 localhost haproxy[47]: Proxy http started.
Nov  3 20:27:37 localhost haproxy[47]: Proxy https started.
Nov  3 20:27:37 localhost haproxy[47]: Proxy mqtt started.
Nov  3 20:27:37 localhost haproxy[47]: Proxy manager_backend started.
Nov  3 20:27:37 localhost haproxy[47]: Proxy keycloak_backend started.
Nov  3 20:27:37 localhost haproxy[48]: keycloak_backend/proxy_backend_host chang                                                                             ed its IP from  to 172.18.0.2 by docker_resolver/dns.
Nov  3 20:27:37 localhost haproxy[48]: Server keycloak_backend/proxy_backend_hos                                                                             t ('keycloak') is UP/READY (resolves again).
Nov  3 20:27:37 localhost haproxy[48]: Server keycloak_backend/proxy_backend_hos                                                                             t administratively READY thanks to valid DNS answer.
Nov  3 20:27:37 localhost haproxy[48]: mqtt/proxy_backend_host changed its IP fr                                                                             om  to 172.18.0.3 by docker_resolver/dns.
Nov  3 20:27:37 localhost haproxy[48]: Server mqtt/proxy_backend_host ('manager'                                                                             ) is UP/READY (resolves again).
Nov  3 20:27:37 localhost haproxy[48]: Server mqtt/proxy_backend_host administra                                                                             tively READY thanks to valid DNS answer.
Nov  3 20:27:37 localhost haproxy[48]: manager_backend/proxy_backend_host change                                                                             d its IP from  to 172.18.0.3 by DNS cache.
Nov  3 20:27:37 localhost haproxy[48]: Server manager_backend/proxy_backend_host                                                                              ('manager') is UP/READY (resolves again).
Nov  3 20:27:37 localhost haproxy[48]: Server manager_backend/proxy_backend_host                                                                              administratively READY thanks to valid DNS answer.
[INFO][2021-11-03 20:27:37] HAProxy started with /etc/haproxy/haproxy.cfg config                                                                             , pid 48.HAPROXY_CERT_FILE
[INFO][2021-11-03 20:27:37] Executing cron_auto_renewal_init at Wed, 03 Nov 2021                                                                              20:27:37 +0000
[INFO][2021-11-03 20:27:37] Domain is 'localhost', dummy SSL certificate does no                                                                             t have to be renewed
[INFO][2021-11-03 20:27:37] Monitoring config file /etc/haproxy/haproxy.cfg and                                                                              certs in /deployment/letsencrypt/live for changes...
[INFO][2021-11-04 12:40:34] DOMAINNAME: localhost
[INFO][2021-11-04 12:40:34] LOCAL_CERT_FILE:
[INFO][2021-11-04 12:40:34] HAPROXY_CERT_FILE: /opt/selfsigned/localhost.pem
[INFO][2021-11-04 12:40:35] HAPROXY_CONFIG: /etc/haproxy/haproxy.cfg
[INFO][2021-11-04 12:40:35] HAPROXY_CMD: haproxy -f /etc/haproxy/haproxy.cfg  -D                                                                              -p /var/run/haproxy.pid
[INFO][2021-11-04 12:40:35] HAPROXY_USER_PARAMS:
[INFO][2021-11-04 12:40:35] PROXY_LOGLEVEL: notice
[INFO][2021-11-04 12:40:35] LE_CERT_ROOT: /deployment/letsencrypt/live
[INFO][2021-11-04 12:40:35] LE_ARCHIVE_ROOT: /deployment/letsencrypt/archive
[INFO][2021-11-04 12:40:35] LE_RENEWAL_CONFIG_ROOT: /deployment/letsencrypt/rene                                                                             wal
[INFO][2021-11-04 12:40:35] LE_CMD: /usr/bin/certbot certonly --config-dir /depl                                                                             oyment/letsencrypt -w /deployment/acme-webroot
[INFO][2021-11-04 12:40:35] LOGFILE: /var/log/proxy.log
rsyslogd: pidfile '/var/run/rsyslogd.pid' and pid 40 already exist.
If you want to run multiple instances of rsyslog, you need to specify
different pid files for them (-i option).
rsyslogd: run failed with error -3000 (see rsyslog.h or try http://www.rsyslog.c                                                                             om/e/3000 to learn what that number means)
Starting enhanced syslogd: rsyslogd already started.
[INFO][2021-11-04 12:40:35] Checking HAProxy configuration: /etc/haproxy/haproxy                                                                             .cfg
Configuration file is valid
[info] 307/124035 (44) : [acme] http-01 plugin v0.1.1
[INFO][2021-11-04 12:40:35] HAProxy started with /etc/haproxy/haproxy.cfg config                                                                             , pid 45.HAPROXY_CERT_FILE
[INFO][2021-11-04 12:40:35] Executing cron_auto_renewal_init at Thu, 04 Nov 2021                                                                              12:40:35 +0000
[INFO][2021-11-04 12:40:35] Domain is 'localhost', dummy SSL certificate does no                                                                             t have to be renewed
[INFO][2021-11-04 12:40:35] Monitoring config file /etc/haproxy/haproxy.cfg and                                                                              certs in /deployment/letsencrypt/live for changes...

Thanks in advance for your help

That is the log of the proxy container; I’m guessing the manager container is the unhealthy container so that log is needed.

There was a breaking schema change the other day which was mentioned in this thread, this might be causing your problems if trying to use an existing DB (logs should show this):

Ahhh alright, that could be the problem indeed. I removed the docker images, docker container and volumes. After the removal I pulled again. This did the trick for me.

Thanks for the reply