generated warnings while checking SSL certificates

[xml]

After I moved from dedicated server to VPS i am receiving daily email with this message:
"The system will not install the certificate from the cPanel Store because the certificate does not support the hostname".

although the certificate is working on the domain and I can see the lock before https://

 

[cPRex]

Hey there! In the past, this has been resolved by "resetting" the hostname on the operating system itself to what it already is. Can you try running this command on the server?

/usr/local/cpanel/bin/set_hostname host.domain.com

where "host.domain.com" is your server's hostname?

Let me know if that fixes the issue!

 

[xml]

[[email protected] ~]# /usr/local/cpanel/bin/set_hostname host.my domain.com
Changing hostname to indexsignal.indexsignal.com...Success!

Hostname set to: host.my domain.com

Warnings were seen during rename:

The hostname was already set to host.my domain.com, syncing configuration only.

Output during rename:

Stopping cPHulkd during hostname change
Service “cphulkd” is already stopped.
Startup Log
        Jan 31 01:04:12 host.my domain.com systemd[1]: Starting cPanel brute force detector services...
        Jan 31 01:04:12 host.my domain.com systemd[1]: cphulkd.service: Failed with result 'protocol'.
        Jan 31 01:04:12 host.my domain.com systemd[1]: Failed to start cPanel brute force detector services.
cphulkd stopped successfully.
Stopping MySQL during hostname change
Changing hostname in kernel to host.my domain.com
Altered hostname in /etc/sysconfig/network
Updating cPHulkd

Updating mailman

Starting cPHulkd

Restarting Exim

Updating cPanel license...Done. Update succeeded.

A DNS record already exists for “host.my domain.com”.
Gracefully restarting queueprocd...
Waiting for “queueprocd” to restart gracefully ……waiting for “queueprocd” to initialize ………finished.

Service Status
        queueprocd (/usr/local/cpanel/libexec/queueprocd --reexec --systemd) is running as root with PID 815 (systemd+/proc check method).

Startup Log
        Jan 31 01:04:02host.my domain.com systemd[1]: Starting cPanel Queue services...
        Jan 31 01:04:03 host.my domain.com startqueueprocd[815]: ==> cPanel TaskQueue Processing Daemon version 1.0
        Jan 31 01:04:03 host.my domain.com systemd[1]: Started cPanel Queue services.

queueprocd restarted successfully.
The system has queued the hostname changes for the Horde and DAV services.
Users cannot access the Horde or DAV features that use these services until
the system has finished updates to the hostname. After the system adjusts a
specific user’s database, it restores their access to the Horde and DAV services.

You will receive a notification when the system completes the update for all users.
.

Then I recieved this email
"The system failed to acquire a signed certificate from the cPanel Store because of the following error: “host.my domain.com” failed DCV. Cannot proceed."

 

[cPRex]

Hey, that's progress! At least the system thinks your hostname is real now, but it just can't complete the DCV check.

Can you reach the following directory on your server?

http://host.domain.com/.well-known/pki-validation/

Depending on your Apache settings you'll either get a directory listing or an error, but if that page can't be displayed properly the DCV check will not complete.

 

[xml]

This is what I get
This site can't be reached took too long to respond.

I forgot to mention I am on KVM VPS

 

[cPRex]

That's like the issue then - you'll need to work with your hosting provider or datacenter to see why the connection to the hostname isn't working. Alternatively you can submit a ticket to our team and we'd be happy to look into that on our end. If you do submit a ticket with our team, please post the ticket number here so I can follow along.

 

[xml]

Hey, that's progress! At least the system thinks your hostname is real now, but it just can't complete the DCV check.

Can you reach the following directory on your server?

http://host.domain.com/.well-known/pki-validation/

Depending on your Apache settings you'll either get a directory listing or an error, but if that page can't be displayed properly the DCV check will not complete.

This is what I got:

 

[cPRex]

Great - that indicates the page can be reached properly from the internet.

Since that is now working, is the DCV check also passing?

 

[xml]

There was a typo on assigned IP address for A record of the hostname and after correction and propagation:


I guess the issue is resolved now

 

[cPRex]

An IP address typo would definitely keep things from working normally. I'm glad you were able to get that working!