nie wiem czy o to prosiłeś ale liczę że taklesny8 wrote: Thu Jun 25, 2020 9:22 pm Poradnik był pisany trochę czasu temu, kiedy dystrybucją na RPi było strech. Niemniej jednak na busterze też bez problemu można wszystko postawić. Teraz Raspbian się przechrzcił na Raspberry Pi OS i jak u Ciebie widać, też wszystko hula.
Przekierowania portów masz, Konfig wygląda ok.
Kontenery wystartowały prawidłowo, żaden się nie restartuje.
Problem miałeś po stronie przeglądarki. Skrypty połącz dopiero jak będziesz miał chociażby jedno urządzenie zarejestrowane w Cloud.
Certyfikaty zostały wystawione? Jak nie to sprawdź logi kontenerów proxy.
Code: Select all
docker logs --tail=50 nginx-letsencrypt
Creating/renewal scr.suplauherce.online certificates... (scr.suplauherce.online)
2020-06-25 20:32:06,266:INFO:simp_le:1414: Generating new certificate private key
2020-06-25 20:32:35,371:ERROR:simp_le:1396: 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-v02.api.letsencrypt.org/acme/authz-v3/5475851725
Challenge validation has failed, see error log.
Debugging tips: -v improves output verbosity. Help is available under --help.
/app
/etc/nginx/certs/suplauherce.online /app
Creating/renewal suplauherce.online certificates... (suplauherce.online)
2020-06-25 20:32:37,893:INFO:simp_le:1414: Generating new certificate private key
2020-06-25 20:32:57,425:ERROR:simp_le:1396: 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-v02.api.letsencrypt.org/acme/authz-v3/5475855695
Challenge validation has failed, see error log.
Debugging tips: -v improves output verbosity. Help is available under --help.
/app
Sleep for 3600s
/etc/nginx/certs/scr.suplauherce.online /app
Creating/renewal scr.suplauherce.online certificates... (scr.suplauherce.online)
2020-06-25 21:33:00,235:INFO:simp_le:1414: Generating new certificate private key
2020-06-25 21:33:21,611:ERROR:simp_le:1396: 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-v02.api.letsencrypt.org/acme/authz-v3/5476658788
Challenge validation has failed, see error log.
Debugging tips: -v improves output verbosity. Help is available under --help.
/app
/etc/nginx/certs/suplauherce.online /app
Creating/renewal suplauherce.online certificates... (suplauherce.online)
2020-06-25 21:33:24,071:INFO:simp_le:1414: Generating new certificate private key
2020-06-25 21:33:54,241:ERROR:simp_le:1396: 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-v02.api.letsencrypt.org/acme/authz-v3/5476665226
Challenge validation has failed, see error log.
Debugging tips: -v improves output verbosity. Help is available under --help.
/app
Sleep for 3600s
/etc/nginx/certs/scr.suplauherce.online /app
Creating/renewal scr.suplauherce.online certificates... (scr.suplauherce.online)
2020-06-25 22:33:57,107:INFO:simp_le:1414: Generating new certificate private key
ACME server returned an error: urn:ietf:params:acme:error:serverInternal :: The server experienced an internal error :: Error retrieving account "https://acme-v02.api.letsencrypt.org/acme/acct/89755293"
Debugging tips: -v improves output verbosity. Help is available under --help.
/app
/etc/nginx/certs/suplauherce.online /app
Creating/renewal suplauherce.online certificates... (suplauherce.online)
2020-06-25 22:34:12,186:INFO:simp_le:1414: Generating new certificate private key
2020-06-25 22:34:35,128:ERROR:simp_le:1396: 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-v02.api.letsencrypt.org/acme/authz-v3/5477543252
Challenge validation has failed, see error log.
Debugging tips: -v improves output verbosity. Help is available under --help.
/app
Sleep for 3600s
: 
cz->b 
+ila
Kto widział ten wie 