Certbot not working: connection refused about docker-easy-haproxy HOT 5 OPEN

Yes, master is the development version and it means is "latest" one.

It seems the labels defined are wrong because it is getting -DOMAIN- instead of the proper domain name to get the certificate.

Could you share your docker-compose file?

from docker-easy-haproxy.

The actual domain was there, I just censored it in the message.

from docker-easy-haproxy.

OK. I apologize for that. :) So, may I have your docker-compose with censored parts?

from docker-easy-haproxy.

Sure! It looks like this:

version: "3"

services:
  echo:
    image: ealen/echo-server:latest
    pull_policy: always
    restart: always
    labels:
      - easyhaproxy.echo.host=domain.org
      - easyhaproxy.echo.port=80
      - easyhaproxy.echo.localport=80
      - easyhaproxy.echo.certbot=true

  easyhaproxy:
    image: byjg/easy-haproxy:master
    pull_policy: always
    restart: always
    ports:
      - 80:80
      - 443:443
    environment:
      - [email protected]
      - EASYHAPROXY_DISCOVER=docker
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

from docker-easy-haproxy.

It is a pretty standard configuration, so nothing from this side. I can try to reproduce this error later today.

Meanwhile, please verify:

• if both the ports 80 and 443 are publicly available
• The domain.org (redacted) needs to have the proper IP setup to the server
• There is no WAF (e.g. Cloudflare) in front of the server IP.
• If your EasyHAProxy server is in a private network instead of a public network, make sure you are doing the proper NAT from the public IP to the private IP/port.

from docker-easy-haproxy.