Hostinger certbot

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: waltify.com

I ran this command: sudo certbot --nginx -d jenkins.waltify.com

It produced this output: Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: jenkins.waltify.com
Type: dns
Detail: no valid A records found for jenkins.waltify.com; no valid AAAA records found for jenkins.waltify.com

My web server is (include version): a Virtual Machine

The operating system my web server runs on is (include version): Ubuntu Server 22.04

My hosting provider, if applicable, is: Local

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

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

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

Hello @Walt-20, welcome to the Let's Encrypt community. :slightly_smiling_face:

Seeing the above indicates the use of HTTP-01 challenge yet you state

I assume you thought you were trying to do DNS-01 challenge, correct?

Given the DNS Records shown below the HTTP-01 challenge is not possible since the IPv4 address of 192.168.122.193 is part of IPv4 Private Address Space and Filtering - American Registry for Internet Numbers

Edit:
Also from here User Guide — Certbot 2.11.0.dev0 documentation please search for --preferred-challenges.

2 Likes

Thanks @Bruce5051, this is my first time spinning up a VM and trying to create a server on my local machine. (figure it is cheaper than AWS)

I will give your guidance a try and let you know how it goes.

EDIT: I am unsure of whether I should do an HTTP-01 or DNS-01 challenge. I am trying to add TLS to this server.

1 Like

@Walt-20 do you want your site publicly accessible?
Then the IP Address must not be in the IPv4 Private Address Space and Filtering - American Registry for Internet Numbers. You would then be able to use the more common HTTP-01 challenge.

Now if you want a certificate containing a wildcard domain name then DNS-01 is required,
if you want to not have the site publicly accessible (and keep the present IPv4 Address of 192.168.122.193) then DNS-01 is only challenge left for getting a Let’s Encrypt issued certificate.

2 Likes

Okay, understood. Thank you

2 Likes