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.
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
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.