Get Error while expand new domain in exist certifiate

[montecarlocode]

I configured ssl cert for 5 domains with letsencrypt on linux server.
now I'm going to add new domain to this cert.
so I used following command:
docker run --rm -p 80:80 -p 443:443 -v /root/nginx/letsencrypt:/etc/letsencrypt certbot/certbot certonly --no-eff-email --email admin@example.com --agree-tos -d example.com -d www.example.com -d chat.example.com -d dev.example.com -d affiliates.example.com -d devaffiliates.example.com --standalone

but I get following error:

that domain authed in dns service and I can create cert for only origin 5 dns.
all dns hosted on same server.
server configured with nginx.
hope your kindly helps.

[MikeMcQ]

Could this be the explanation for EOFError?

EOFError running certbot with docker

I…

[_az]

That should work. You can also try docker run with the -it flags, so that permits you to do interactive things.

[montecarlocode]

thanks for your reply>

I use updated command and get success string
docker run -it --rm -p 80:80 -p 443:443 -v /root/nginx/letsencrypt:/etc/letsencrypt certbot/certbot certonly --no-eff-email --email admin@betbit.com --agree-tos -d betbit.com -d www.betbit.com -d chat.betbit.com -d dev.betbit.com -d affiliates.betbit.com -d devaffiliates.betbit.com  --standalone --expand

but I can't see site till now.

[MikeMcQ]

You must use HTTPS:// and it should work fine (see below).

You chose to use --standalone which uses port 80 (HTTP) for the cert challenge. If you want HTTP to work for your web server you need to review your configuration.

curl -I -m8 https://devaffiliates.betbit.com
HTTP/1.1 404 Not Found
Server: nginx/1.16.1
X-Powered-By: PHP/8.1.15

curl -I -m8 http://devaffiliates.betbit.com
curl: (52) Empty reply from server

[Bruce5051]

Looks like you got a certificate with all 6 domain names and they are working.

Here is a list of issued certificates crt.sh | betbit.com, the latest being 2023-02-12;
With these Matching Identities:

1. affiliates.betbit.com
2. betbit.com
3. chat.betbit.com
4. devaffiliates.betbit.com
5. dev.betbit.com
6. www.betbit.com

https://www.ssllabs.com/ssltest/analyze.html?d=betbit.com

https://www.ssllabs.com/ssltest/analyze.html?d=affiliates.betbit.com

https://www.ssllabs.com/ssltest/analyze.html?d=chat.betbit.com

https://www.ssllabs.com/ssltest/analyze.html?d=dev.betbit.com

https://www.ssllabs.com/ssltest/analyze.html?d=devaffiliates.betbit.com

https://www.ssllabs.com/ssltest/analyze.html?d=www.betbit.com

[MikeMcQ]

@Bruce5051

Looks like you got a certificate with all 6 domain names and they are working.

Yes, it was the HTTP request in the browser that failed (not HTTPS).

[montecarlocode]

Resolved.
cause is domain propagation.
dns service actived domain devaffiliates.betbit.com after 48 hours.
thanks your kindly reply.