Replies: 1 comment
-
weirdly enough, it started to work. It was probably some DNS caching |
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
-
Hello, I am trying to add an ssl certificate to my website using kamal but it's not working. I have a domain bought on register.it (let's called it domain.com) and an hosting on hetzner.com (with IP let's say 65.10.10.10). I have added an A Record on register.it that points to my hosting on Hetzner. Whithout HTTPS, the DNS where correctly redirecting from my domain to my hosting. After I have added the let's encrypt section to my deploy.yml file, the DNS started to point to some Amazon ISP servers (3.33.130.190 - IP Info - AWS Global Accelerator and the same for 15.197.148.33), I think as a consequence of the fact that letsencrypt is not set up properly.
This is my relevant part of the deploy.yml file with let's encrypt enabled (crafted after reading this #112).
The /letsencrypt/acme.json file is populated after the deploy, has 600 permissions and belongs to the same user running docker and kamal.
Port 80 for my ip 65.10.10.10 is open, I can verify with ncat.
PORT STATE SERVICE
80/tcp open http
Also, I am aware that I could use the DNS challenge, but my provider does not have an API to update the TXT record, therefore I would like to avoid it, if possible.
Any idea about what am I doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions