Certbot with a Siebel Linux Application Server

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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My Note: Siebel using certificate trust stores where a Linux Server Certificate is create for the server and the imported into the trust stores. There is no native Apache server for Certbot to check port 80 as port 80 and 443 are not supported by the application but ports like 90xx, 96xx and 96xx.

My domain is: This is an internal Linux Server Certificate for this case it is vldctmxxxss.dhe.duke.edu

I ran this command: sudo certbot certonly --standalone

It produced this output:Requesting a certificate for vwdctmsssd11.dhe.duke.edu

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: vwdctmsssd11.dhe.duke.edu
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for vwdctmsssd11.dhe.duke.edu - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for vwdctmsssd11.dhe.duke.edu - check that a DNS record exists for this domain

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.

My web server is (include version):

The operating system my web server runs on is (include version):Operating System: Red Hat Enterprise Linux 8.10 (Ootpa)
CPE OS Name: cpe:/o:redhat:enterprise_linux:8::baseos
Kernel: Linux 4.18.0-553.60.1.el8_10.x86_64
Architecture: x86-64

My hosting provider, if applicable, is:

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):

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

Is that vwdctmsssd11.dhe.duke.edu hostname also only internally resolvable?

Because Let's Encrypt is a publicly trusted CA. It requires the hostname to be in the public DNS to be able to validate it.

3 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.