First run of docker container and ssl certificate is shown in-secure

[songlet]

[remach]

Check environment variables LETSENCRYPT_HOST: ${DOMAINS} LETSENCRYPT_EMAIL: ${LETSENCRYPT_EMAIL}

[songlet]

Check environment variables LETSENCRYPT_HOST: ${DOMAINS} LETSENCRYPT_EMAIL: ${LETSENCRYPT_EMAIL}

Checked, they are input properly; should I register them-domain and email in advance through letsencrypt.org?

[remach]

Yes, the domain should be registered and point to your server where nginx works. Instead you can't pass Acme challenge. No action at letsencrypt.org needed.

[songlet]

I received the following error in the log on nginx-letsencrypt：

CA marked some of the authorizations as invalid, which likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in -d example.com:path or --default_root? Are all your domains accessible from the internet? Please check your domains' DNS entries, your host's network/firewall setup and your webserver config. If a domain's DNS entry has both A and AAAA fields set up, some CAs such as Let's Encrypt will perform the challenge validation over IPv6. If your DNS provider does not answer correctly to CAA records request, Let's Encrypt won't issue a certificate for your domain (see https://letsencrypt.org/docs/caa/). Failing authorizations: https://acme-v01.api.letsencrypt.org/acme/authz/p8hCxS31YD1dXBQDb56DxEIyaijw-vMLDGyW7QI3CpM

[songlet]

Yes, the domain should be registered and point to your server where nginx works. Instead you can't pass Acme challenge. No action at letsencrypt.org needed.

http works,but https not.

[remach]

I suppose that you leave example.com at the .env file. It will be helpful if you can share the real yml And .env .

On Fri, 12 Jul 2019 at 15:28, songlet notifications@github.com wrote:

Yes, the domain should be registered and point to your server where nginx works. Instead you can't pass Acme challenge. No action at letsencrypt.org needed.

http works,but https not.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/evertramos/docker-wordpress-letsencrypt/issues/37?email_source=notifications&email_token=AABWZBRYID5RMJQJ5HGGM3TP7B2IFA5CNFSM4ICGUSK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZZTVFY#issuecomment-510868119, or mute the thread https://github.com/notifications/unsubscribe-auth/AABWZBSNWHLB3EYSQUOZO4LP7B2IFANCNFSM4ICGUSKQ .

-- Краснов Дмитрий +7 926 567 81 82

[songlet]

Sure

I put the IP address :0.0.0.0 as it it ; is it required to change to my specific external IP address (AWS) instead?

[songlet]

I suppose that you leave example.com at the .env file. It will be helpful if you can share the real yml And .env . On Fri, 12 Jul 2019 at 15:28, songlet @.***> wrote: Yes, the domain should be registered and point to your server where nginx works. Instead you can't pass Acme challenge. No action at letsencrypt.org needed. http works,but https not. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#37?email_source=notifications&email_token=AABWZBRYID5RMJQJ5HGGM3TP7B2IFA5CNFSM4ICGUSK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZZTVFY#issuecomment-510868119>, or mute the thread https://github.com/notifications/unsubscribe-auth/AABWZBSNWHLB3EYSQUOZO4LP7B2IFANCNFSM4ICGUSKQ . -- Краснов Дмитрий +7 926 567 81 82

Please close this issue as it is resolved after I changed my email address for the Lets Encrypt email.