certbot - Connection Reset by Peer

Questions / Help
1

I’ve been trying to deploy a container for several hours and am getting stuck on obtaining a certificate with certbot.

Every time, I get the same error “Connection reset by peer.”

After switching operating systems (first Debian, then Ubuntu, now Alpine Linux), switching between three different domains (since I thought HSTS preload could be the problem) I’ve finally been locked out by Let’s Encrypt for too many attempts.

Does anyone have any clue what this could be? I’ve confirmed that the IP addresses match up to my domain name (both IPv4, IPv6) for what it’s worth.

Dockerfile:

FROM alpine:latest

RUN apk update && apk upgrade && apk add ca-certificates certbot ruby unbound

COPY data/ /

RUN chmod 0644 /etc/cron.d/certbot
RUN chmod 0644 /etc/cron.d/dns-sniper

RUN crontab /etc/cron.d/certbot
RUN crontab /etc/cron.d/dns-sniper

RUN gem install --pre dns-sniper

EXPOSE 80/tcp

RUN certbot certonly --standalone \
                     --agree-tos -m [EMAIL] \
                     --non-interactive \
                     -d [DOMAIN] \
                     -v

[SHORTENED BECAUSE CRASH HAPPENS HERE]

fly.toml:

app = "[NAME]"
kill_signal = "SIGINT"
kill_timeout = 5
processes = []

[env]

[experimental]
  allowed_public_ports = [80, 853]
  auto_rollback = true

[[services]]
  internal_port = 80
  processes = ["app"]
  protocol = "tcp"
  script_checks = []

  [services.concurrency]
    hard_limit = 25
    soft_limit = 20
    type = "connections"

  [[services.ports]]
    handlers = ["tcp"]
    port = 80

[[services]]
  internal_port = 853
  processes = ["app"]
  protocol = "tcp"
  script_checks = []

  [services.concurrency]
    hard_limit = 25
    soft_limit = 20
    type = "connections"

  [[services.ports]]
    handlers = ["tcp"]
    port = 853