K8s Can't recreate certificates for domain demo.neoflex-tech.ru

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: demo.neoflex-tech.ru

I ran this command: sudo certbot certonly --standalone -d demo.neoflex-tech.ru

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for demo.neoflex-tech.ru

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: demo.neoflex-tech.ru
Type: connection
Detail: 176.57.218.216: Fetching http://demo.neoflex-tech.ru/.well-known/acme-challenge/mbaUWOUgfPQs8dnddoo-fW474gFuCFi7z2IKa4GLYGs: Connection refused

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): nginx version: nginx/1.21.6

The operating system my web server runs on is (include version): inside pod kubernetes -
Linux ingress-nginx-controller-qdxf2 5.15.0-122-generic #132-Ubuntu SMP Thu Aug 29 13:45:52 UTC 2024 x86_64 Linux

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know): probably yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): -

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 3.1.0

I don't know very much about Kubernetes. But, usually people use cert-manager with it.

Can you explain why you are using Certbot instead? And, usually with Certbot if you have an active nginx server you would not use --standalone option. The --standalone option requires exclusive use of port 80.

Is that how you got your first cert back in October? Did you have Kubernetes setup and working then?

3 Likes