Problem on Shared-IP server

Help
1

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 domain is:
kukumo.net

I ran this command:
from directAdmin -> install SSL certificate

It produced this output:
Requesting new certificate order…
Nonce is empty. Exiting. dig output of acme-v02.api.letsencrypt.org:
api.letsencrypt.org-ng.edgekey.net.
e14990.dscx.akamaiedge.net.
23.77.106.26

My web server is (include version):
Apache (2.4.39)

The operating system my web server runs on is (include version):
CentOS (7.2)

My hosting provider, if applicable, is:
VPS with sharedIP

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):
DirectAdmin (1.57.2)

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

PROBLEM:
i switched my old VPS to a New CentOS7, which supports multicertificates on same IP (190.105.227.167).
I successfully added LetsEncrypt certificate on 3 Domains with this IP (vecinosenred.net, ecampus.net, edupatagonia.com.ar), but im getting this error on my MAIN domain (kukumo.net) with same IP.

thanks in advance!

2

Hi @tomich

looks like your hosts file has a fixed ip address that's now wrong.

Something like

23.77.106.26          acme-v02.api.letsencrypt.org

so your server uses a hard coded ip address.

3

my “/etc/hosts” file seems ok, it has the following:

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
190.105.227.167 server.kukumo.net

4

Searched, found that.

Looks like your curl is too old.

5

The thing is that regular domains did got encripted successfully, only the main admin domain didn’t.

Anyway… following code fixed the problem, thanks a lot JuergenAuer!!! :raised_hands:

cd /usr/local/directadmin/custombuild
./build update
./build curl
1 Like
6

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