New setup (pro) letsencrypt fails with no route to host


I’m tryning to set up small seafile pro for lab, so that’s why I’m using docker version. Unfortunately I can’t get ir running with tls enabled.
When starting seafile container dies after few seconds.
If I take a look at docker log, I can see that verification fails with message - no route to host.

If I install certbot manually inside seafile containter, everthing works well, only issue is - I can’t restart container, as all setup is lost after restart. But anyway that shows there is no connections error in general. Perhaps something is not correct in /scripts/ script.

How can I get ir up and running with ssl enabled?

Error message:
Already up to date.
Parsing account key…
Parsing CSR…
Found domains: <my_real_domain>
Getting directory…
Directory found!
Registering account…
Already registered!
Creating new order…
Order created!
Verifying <my_real_domain>…
Traceback (most recent call last):
File “/shared/ssl/letsencrypt/”, line 198, in
File “/shared/ssl/letsencrypt/”, line 194, in main
signed_crt = get_crt(args.account_key, args.csr, args.acme_dir, log=LOGGER,, disable_check=args.disable_check, directory_url=args.directory_url,
File “/shared/ssl/letsencrypt/”, line 144, in get_crt
raise ValueError(“Wrote file to {0}, but couldn’t download {1}: {2}”.format(wellknown_path, wellknown_url, e))
ValueError: Wrote file to /var/www/challenges/1Cx0bMduGQ0bLTtSUdt0azQFlVXAiuGKd3jnRSI6R1k, but couldn’t download http://<my_real_domain>/.well-known/acme-challenge/1Cx0bMduGQ0bLTtSUdt0azQFlVXAiuGKd3jnRSI6R1k: Error:
Url: http://<my_real_domain>/.well-known/acme-challenge/1Cx0bMduGQ0bLTtSUdt0azQFlVXAiuGKd3jnRSI6R1k
Data: None
Response Code: None
Response: <urlopen error [Errno 113] No route to host>

Just a gues… It sounds like the ACME challenge cant be downlaoded by lets encrypt (by their servers probabbly?).

Is the A/AAAA record public routable?