-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
503 - Service Unavailable #175
Comments
I also have the same problem, did you manage to solve it, @ersinpw how did you solve it? Thanks. |
I have the same problem, I am testing everything on localhost, that is, within a virtual machine, the haproxy.conf file I have changed the name of the service to the ip of the vm 192.168.10.14, leaving it like this: global defaults frontend http-in acl is_cert_validation path -i -m beg "/.well-known/acme-challenge/" acl host_api hdr_dom(host) -i "api.${HAPROXY_HOSTNAME}" acl host_registry hdr_dom(host) -i "registry.${HAPROXY_HOSTNAME}" acl host_vpn hdr_dom(host) -i "vpn.${HAPROXY_HOSTNAME}" acl host_s3 hdr_dom(host) -i "s3.${HAPROXY_HOSTNAME}" frontend ssl-in acl is_ssl req.ssl_ver 2:3.4 acl host_tunnel req_ssl_sni -i "tunnel.${HAPROXY_HOSTNAME}" use_backend redirect-to-https-in if is_ssl backend redirect-to-https-in backend redirect-to-tunnel-in frontend https-in acl host_api hdr_dom(host) -i "api.${HAPROXY_HOSTNAME}" acl host_registry hdr_dom(host) -i "registry.${HAPROXY_HOSTNAME}" acl host_vpn hdr_dom(host) -i "vpn.${HAPROXY_HOSTNAME}" acl host_s3 hdr_dom(host) -i "s3.${HAPROXY_HOSTNAME}" backend backend_api backend backend_registry backend backend_vpn backend backend_s3 backend cert-provider backend vpn-devices frontend db backend backend_db frontend redis backend backend_redis listen vpn-tunnel listen vpn-tunnel-tls being the solution to these errors: Building certificate from environment variables... and now the errors I have left to resolve are: (input): docker logs -f openbalena_haproxy_1 (output): The local domain configured is openbalena.local, if I enter www.openbalena.local configuring that address in /etc/hosts, the error is the following: 503 Service Unavailable I would appreciate your help in solving this problem Greetings @ersinpw @luisgs7 (speak spanish?, i from chile) @wrboyce @relaxdiego @dfunckt |
@ersinpw Thanks for the mentioning. If you have a working setup which results into a haproxy service running in a container can you please share the logs from the failing HAproxy service? Moreover, are we more than happy for contributions to maintain this project, as the current pinned HAproxy version itself is fairly outdated. Thanks and best regards |
This message:
shows that the docker-compose environment isn't able to resolve the service names for the inter-service communication. open-balena/src/haproxy/haproxy.cfg Line 76 in ea07d43
The haproxy container only knows about name api and the underlying docker / docker-compose environment has to resolve the api to the actual other service running as container.
Please try to narrow down if the docker / docker-compose environment is able to communicate with each other and resolve services names. |
I followed the following docs page very precisely: https://www.balena.io/open/docs/getting-started/
This is my third try, however I stuck every time at the step where the openBalena server is tested. The services that runs on port 80 and 443 returns:
Therefore the ping with curl fails also and returns the same.
I am running everything on a brand new Ubuntu 18.04 x64 server.
Edit:
I see lots of people with the same issue. I did a deeper investigation and it seems that the "openbalena_haproxy" container is not working properly. When I open a bash to the container:
docker exec -it e7eae59bbe09 /bin/sh
and fetch the page at 0.0.0.0
wget 0.0.0.0
it returns the same 503 Service unavailable page
The text was updated successfully, but these errors were encountered: