SSL issues after server migration

[pqpier]

So I had a WHM/cPanel on a cloud server and I migrated over to a dedicated server.

There is some issue with the SSL.
I was using lets encrypt in the cloud server and am using it again in the new server.

It looks like upon account creation and/or domain added, self-signed certificates are not being generated.

So all users were seeing content from another user. I went to the SSL hosts thing and made my own domain as primary.
So at least now they don't see another users content, but issue persists.

Some domains are never getting SSLed through auto ssl... Some other show the SSL was installed, domain is OK, but when I open the website, it shows like certificate is from my domain and not the users domain.

If I try to install certificate via LE plugin on their cpanel acc, it seems to work but it doesnt change anything.

If try to install via install certificate on WHM Panel, I get the following error:

API failure: Missing “cert”! at /usr/local/cpanel/Cpanel/SSL/Objects/Certificate.pm line 36.

 

[cPRex]

Hey there! If you manually check the Apache configuration, can you confirm that there is no vhost on port 443 for the domains that are experiencing this issue? If that's the case, there could be an issue with the account creation process, or the Apache configuration, and we'd likely need a support ticket created to dig into those.

 

[pqpier]

I forgot to mention I am using Litespeed on this server.

Hey there! If you manually check the Apache configuration, can you confirm that there is no vhost on port 443 for the domains that are experiencing this issue? If that's the case, there could be an issue with the account creation process, or the Apache configuration, and we'd likely need a support ticket created to dig into those.

 

[cPRex]

cPanel still creates and reads data from the Apache configuration file, so it's still worth checking /etc/apache2/conf/httpd.conf to see if the vhosts themselves are present.

 

[pqpier]

cPanel still creates and reads data from the Apache configuration file, so it's still worth checking /etc/apache2/conf/httpd.conf to see if the vhosts themselves are present.

I checked now and vhosts are there, but if I had to guess, I'd say they weren't before.

It looks like it was something with Litespeed.
Things seem to be working fine now after building Litespeed and applying some changes under EasyApache 4 that were automatically suggested or something like that.

I will get back if issue arises with new customers, but the ones the had this problem seem to be sorted out.

 

[cPRex]

I'm glad that's working well now. Let us know if you run into this again!

 

[pqpier]

I'm glad that's working well now. Let us know if you run into this again!

Actually I just ran into the same problem again and I confirmed that there is no vhost.

So what can we do?

 

[cPRex]

Can you submit a ticket to our support team before any other changes are made so we can see the server in this state?

 

[pqpier]

Can you submit a ticket to our support team before any other changes are made so we can see the server in this state?

I'm trying, but I can't get passed the submit button, it says my support access ID is invalid.

I just copied it using /usr/local/cpanel/cpanel -S and logged as root user.

 

[cPRex]

If you have issues with getting it submitted through WHM you can always put one in directly (as you found) or you can email [email protected] to get the process started, although Customer Service may not see the ticket as quickly as Technical Support.

 

[pqpier]

If you have issues with getting it submitted through WHM you can always put one in directly (as you found) or you can email [email protected] to get the process started, although Customer Service may not see the ticket as quickly as Technical Support.

Looks like it's the only option, I copied and filled in the correct info, it says invalid, so what can I do...

 

[cPRex]

Customer Service is still around for a bit tonight, so I'd go that route.

 

[pqpier]

Customer Service is still around for a bit tonight, so I'd go that route.

I sent the email few minutes ago, let's see if I have any luck

 

[cPRex]

Were we able to get that resolved for you or did you still need assistance with this?

 

[pqpier]

Were we able to get that resolved for you or did you still need assistance with this?

Well, turns out my problem was bigger than expected.
You can close this thread.

Thanks.

 

[cPRex]

Well that doesn't sound good, although hopefully we were able to help once you got in touch with our support.