Bad Gateway / Timeout adding ssl #4335
Closed
VinterSolen
started this conversation in
General
Replies: 1 comment
-
hmm. removed the outdated cert and re-ran the cert, and it worked within a few seconds. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I just installed npm in a docker.
Im trying to add ssl cert for a .DEV domain.
I add domain.dev and *.domain.dev. doing dns channelnge on porkbun api.
the txt- fields are added like i expect.
IF: the Propagation Seconds is empty or set to 300/600 i get timeout eventually.
IF the Propagation Seconds is set to like 1400+ after a longer time i get "Bad Gateway"
in both cases, the certbot still runs in the background.
After this bad gateway, i checked the SSL cert page, and it lists a cert for my domains, but expiry is today and ~10 minutes ago (so this cert is invalid already before i get it)
What am i doing wrong?
If i login to the docker console and check /tmp/letsencrupt-log/ files i see this:
Beta Was this translation helpful? Give feedback.
All reactions