Proxy-1 Cannot start proxy until config file errors are resolved in '/etc/haproxy/haproxy.cfg'

vamsi · July 11, 2024, 1:14am

proxy-1 | [ERROR][2024-07-11 00:51:32] Cannot start proxy until config file errors are resolved in ‘/etc/haproxy/haproxy.cfg’

any one please help me. Or not starting normally when i restart the system. iam getting this error. every time i hvae to remove proxy container and reinstallining i am doing.
I install docker Desktop in my windows 10 and pullt the images manually usig docker desktop and use this command to start the or( docker-compose -p openremote up) i am using this yml to start my OR.
docker-compose.txt (2.5 KB)

apurba · July 11, 2024, 4:01am

Change the IP in yml and start the container with localhost and post if there any error.

vamsi · July 11, 2024, 4:50am

thank you very much to reply.

               when i open with this url   (https://localhost/)    its ok ......
                when i open with https://192.168.1.36/  igot error like this...

apurba · July 11, 2024, 4:54am

run this below command and share log of container (Proxy)

docker-compose stop
docker-compose kill
NET stop HTTP

vamsi · July 11, 2024, 5:11am

2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] DOMAINNAMES:
2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] HAPROXY_CONFIG: /etc/haproxy/haproxy.cfg
2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] HAPROXY_CMD: haproxy -W -db -f /etc/haproxy/haproxy.cfg
2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] HAPROXY_USER_PARAMS:
2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] PROXY_LOGLEVEL: notice
2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] LUA_PATH:
2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] CERT_DIR: /deployment/certs
2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] LE_DIR: /deployment/letsencrypt
2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] LE_CMD: certbot certonly -n --logs-dir - -w /etc/haproxy/webroot --register-unsafely-without-email
2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] AWS_ROUTE53_ROLE:
2024-07-11 09:53:23 [INFO][2024-07-11 04:23:23] Checking HAProxy configuration: /etc/haproxy/haproxy.cfg
2024-07-11 09:53:24 [INFO][2024-07-11 04:23:24] Starting crond
2024-07-11 09:53:24 [INFO][2024-07-11 04:23:24] HAProxy starting
2024-07-11 09:53:24 [INFO][2024-07-11 04:23:24] cert_init…waiting 10s for haproxy to be ready
2024-07-11 09:53:24 [NOTICE] (1) : New worker (30) forked
2024-07-11 09:53:24 [NOTICE] (1) : Loading success.
2024-07-11 09:53:24 [WARNING] (30) : keycloak_backend/keycloak changed its IP from (none) to 172.18.0.3 by docker_resolver/dns.
2024-07-11 09:53:24 [WARNING] (30) : Server keycloak_backend/keycloak (‘keycloak’) is UP/READY (resolves again).
2024-07-11 09:53:24 [WARNING] (30) : Server keycloak_backend/keycloak administratively READY thanks to valid DNS answer.
2024-07-11 09:53:24 [WARNING] (30) : mqtt/manager changed its IP from (none) to 172.18.0.4 by docker_resolver/dns.
2024-07-11 09:53:24 [WARNING] (30) : Server mqtt/manager (‘manager’) is UP/READY (resolves again).
2024-07-11 09:53:24 [WARNING] (30) : Server mqtt/manager administratively READY thanks to valid DNS answer.
2024-07-11 09:53:24 [WARNING] (30) : manager_backend/manager changed its IP from (none) to 172.18.0.4 by DNS cache.
2024-07-11 09:53:24 [WARNING] (30) : Server manager_backend/manager (‘manager’) is UP/READY (resolves again).
2024-07-11 09:53:24 [WARNING] (30) : Server manager_backend/manager administratively READY thanks to valid DNS answer.
2024-07-11 09:53:35 Saving debug log to /var/log/letsencrypt/letsencrypt.log
2024-07-11 10:06:39 [NOTICE] (1) : haproxy version is 2.9.7-5742051
2024-07-11 09:53:24 keycloak_backend/keycloak changed its IP from (none) to 172.18.0.3 by docker_resolver/dns.
2024-07-11 09:53:24 Server keycloak_backend/keycloak (‘keycloak’) is UP/READY (resolves again).
2024-07-11 09:53:24 Server keycloak_backend/keycloak administratively READY thanks to valid DNS answer.
2024-07-11 09:53:24 mqtt/manager changed its IP from (none) to 172.18.0.4 by docker_resolver/dns.
2024-07-11 09:53:24 Server mqtt/manager (‘manager’) is UP/READY (resolves again).
2024-07-11 09:53:24 Server mqtt/manager administratively READY thanks to valid DNS answer.
2024-07-11 09:53:24 manager_backend/manager changed its IP from (none) to 172.18.0.4 by DNS cache.
2024-07-11 09:53:24 Server manager_backend/manager (‘manager’) is UP/READY (resolves again).
2024-07-11 09:53:24 Server manager_backend/manager administratively READY thanks to valid DNS answer.
2024-07-11 09:53:34 [INFO][2024-07-11 04:23:34] Executing cert_init at Thu, 11 Jul 2024 04:23:34 +0000
2024-07-11 09:53:34 [INFO][2024-07-11 04:23:34] Executing auto renew at Thu, 11 Jul 2024 04:23:34 +0000
2024-07-11 09:53:35
2024-07-11 09:53:35 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2024-07-11 09:53:35 No renewals were attempted.
2024-07-11 09:53:35 No hooks were run.
2024-07-11 09:53:35 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2024-07-11 09:53:35 [INFO][2024-07-11 04:23:35] Starting monitoring process
2024-07-11 09:53:35 [INFO][2024-07-11 04:23:35] Monitoring config file ‘/etc/haproxy/haproxy.cfg’ and certs in ‘/deployment/certs’ for changes…
2024-07-11 10:06:39 Proxy stats stopped (cumulated conns: FE: 0, BE: 0).
2024-07-11 10:06:39 Proxy http stopped (cumulated conns: FE: 166, BE: 0).
2024-07-11 10:06:39 Proxy https stopped (cumulated conns: FE: 16, BE: 0).
2024-07-11 10:06:39 Proxy mqtt stopped (cumulated conns: FE: 0, BE: 0).
2024-07-11 10:06:39 Proxy manager_backend stopped (cumulated conns: FE: 0, BE: 64).
2024-07-11 10:06:39 [WARNING] (1) : Exiting Master process…
2024-07-11 10:06:39 [WARNING] (30) : Proxy stats stopped (cumulated conns: FE: 0, BE: 0).
2024-07-11 10:06:39 [WARNING] (30) : Proxy http stopped (cumulated conns: FE: 166, BE: 0).
2024-07-11 10:06:39 [WARNING] (30) : Proxy https stopped (cumulated conns: FE: 16, BE: 0).
2024-07-11 10:06:39 Proxy keycloak_backend stopped (cumulated conns: FE: 0, BE: 30).
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] DOMAINNAMES:
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] HAPROXY_CONFIG: /etc/haproxy/haproxy.cfg
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] HAPROXY_CMD: haproxy -W -db -f /etc/haproxy/haproxy.cfg
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] HAPROXY_USER_PARAMS:
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] PROXY_LOGLEVEL: notice
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] LUA_PATH:
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] CERT_DIR: /deployment/certs
2024-07-11 10:06:39 [WARNING] (30) : Proxy mqtt stopped (cumulated conns: FE: 0, BE: 0).
2024-07-11 10:06:39 [WARNING] (30) : Proxy manager_backend stopped (cumulated conns: FE: 0, BE: 64).
2024-07-11 10:06:39 [WARNING] (30) : Proxy keycloak_backend stopped (cumulated conns: FE: 0, BE: 30).
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] LE_DIR: /deployment/letsencrypt
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] LE_CMD: certbot certonly -n --logs-dir - -w /etc/haproxy/webroot --register-unsafely-without-email
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] AWS_ROUTE53_ROLE:
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] Checking HAProxy configuration: /etc/haproxy/haproxy.cfg
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] Starting crond
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] HAProxy starting
2024-07-11 10:09:26 [INFO][2024-07-11 04:39:26] cert_init…waiting 10s for haproxy to be ready
2024-07-11 10:09:26 mqtt/manager changed its IP from (none) to 172.18.0.4 by docker_resolver/dns.
2024-07-11 10:09:26 Server mqtt/manager (‘manager’) is UP/READY (resolves again).
2024-07-11 10:09:26 Server mqtt/manager administratively READY thanks to valid DNS answer.
2024-07-11 10:09:26 manager_backend/manager changed its IP from (none) to 172.18.0.4 by DNS cache.
2024-07-11 10:09:26 Server manager_backend/manager (‘manager’) is UP/READY (resolves again).
2024-07-11 10:09:26 [NOTICE] (1) : New worker (30) forked
2024-07-11 10:09:26 [NOTICE] (1) : Loading success.
2024-07-11 10:09:26 [WARNING] (30) : mqtt/manager changed its IP from (none) to 172.18.0.4 by docker_resolver/dns.
2024-07-11 10:09:26 [WARNING] (30) : Server mqtt/manager (‘manager’) is UP/READY (resolves again).
2024-07-11 10:09:26 [WARNING] (30) : Server mqtt/manager administratively READY thanks to valid DNS answer.
2024-07-11 10:09:26 [WARNING] (30) : manager_backend/manager changed its IP from (none) to 172.18.0.4 by DNS cache.
2024-07-11 10:09:26 [WARNING] (30) : Server manager_backend/manager (‘manager’) is UP/READY (resolves again).
2024-07-11 10:09:26 [WARNING] (30) : Server manager_backend/manager administratively READY thanks to valid DNS answer.
2024-07-11 10:09:26 [WARNING] (30) : keycloak_backend/keycloak changed its IP from (none) to 172.18.0.3 by docker_resolver/dns.
2024-07-11 10:09:26 Server manager_backend/manager administratively READY thanks to valid DNS answer.
2024-07-11 10:09:26 keycloak_backend/keycloak changed its IP from (none) to 172.18.0.3 by docker_resolver/dns.
2024-07-11 10:09:26 Server keycloak_backend/keycloak (‘keycloak’) is UP/READY (resolves again).
2024-07-11 10:09:26 Server keycloak_backend/keycloak administratively READY thanks to valid DNS answer.
2024-07-11 10:09:36 [INFO][2024-07-11 04:39:36] Executing cert_init at Thu, 11 Jul 2024 04:39:36 +0000
2024-07-11 10:09:36 [INFO][2024-07-11 04:39:36] Executing auto renew at Thu, 11 Jul 2024 04:39:36 +0000
2024-07-11 10:09:37
2024-07-11 10:09:37 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2024-07-11 10:09:37 No renewals were attempted.
2024-07-11 10:09:37 No hooks were run.
2024-07-11 10:09:37 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2024-07-11 10:09:37 [INFO][2024-07-11 04:39:37] Starting monitoring process
2024-07-11 10:09:37 [INFO][2024-07-11 04:39:37] Monitoring config file ‘/etc/haproxy/haproxy.cfg’ and certs in ‘/deployment/certs’ for changes…
2024-07-11 10:09:26 [WARNING] (30) : Server keycloak_backend/keycloak (‘keycloak’) is UP/READY (resolves again).
2024-07-11 10:09:26 [WARNING] (30) : Server keycloak_backend/keycloak administratively READY thanks to valid DNS answer.
2024-07-11 10:09:37 Saving debug log to /var/log/letsencrypt/letsencrypt.log

vamsi · July 11, 2024, 5:16am

yes i run the command but iam unable to access the openremote from ip adress.if i put the ip adress of my computer then only i access the OR… but the problem is after restating the system proxy container not starting.

apurba · July 11, 2024, 5:19am

try the same with incognito mode. and press F12

if you want I can connect in any desk.

add below to manager volume

./deployment:/deployment

vamsi · July 11, 2024, 6:01am

1 860 374 448 this is my any desk id.

apurba · July 11, 2024, 6:51am

Now run 2 command in cmd

docker-compose down
docker-compose -p openremote up

system · October 9, 2024, 6:51am

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.