Let's encrypt issues after changing server

Hi everyone,

I took a new server to switch to debian 12, I configured it like the old one by following the perfect server debian 12 tutorial for ISP Config 3 and I transferred all the data from my sites from the old server to the new one, the same for the databases.

Some sites are sent to the new server but not all (including the main one which has the same domain name as the server, that's a real issue :/).

For the sites that are redirected to the new server, I have an SSL certificate problem and when I go to those sites' URIs I get an "unsecured connection" message.

I regenerated the server's SSL certificate with the command "ispconfig_update.sh --force", I unchecked then re-checked the SSL certificate in the site configuration from the ISP Config administration console, but still the same problem.

How can I solve this?

Thanks in advance

 

You should check out https://forum.howtoforge.com/threads/lets-encrypt-error-faq.74179/

Did you use the migration Toolkit or transferred the sites and databases manually?

 

How did you set this up?

 

Thanx pyte

Already did that before creating this thread (and still trying to find a solution with that), but didn't find yet :/

I did it manually with scp, assigning right web numbers to the file (ie. web1, web2, etc.). Some websites are OK, others aren't with the same settings.

I also just saw that some let's encrypt boxes are not keeping the checked status.

 

Hey till,

The output is

Code:

root@server1:~# /usr/local/ispconfig/server/server.sh
PHP Warning:  Trying to access array offset on value of type null in /usr/local/ispconfig/server/plugins-available/apache2_plugin.inc.php on line 851
setquota: Not setting block grace time on /dev/md1 because softlimit is not exceeded.
setquota: Not setting inode grace time on /dev/md1 because softlimit is not exceeded.
[Mon Apr 15 02:10:39 PM CEST 2024] Invalid status, bulbizar.com:Verify error detail:212.83.183.54: Invalid response from http://bulbizar.com/.well-known/acme-challenge/qLurJMUG9L5a-nUwHFkikcP1_EHWqJC9OymQkHt8OOM: 404
[Mon Apr 15 02:10:39 PM CEST 2024] Please check log file for more details: /var/log/ispconfig/acme.log
finished server.php.

The IP Address 212.83.183.54 is wrong (old server), the DNS settings on the new server is OK (right IP Address) and the DN is recorded with the nameserver as primary DNS

For another website (with .fr extension) I don't have the same error, but the problem is the same.

 

Thx till

All my domain's DNS records are pointing to server1.myserver.com (which is the name of the server, 'myserver' is not the real name). The problem might be that server1.myserver.com is also the name of the old server. But actually everything should point to the new server.

Didn't think of that, so I only have to wait ?

There are so many problems actually, I can't see how it'll work by itself just waiting..

Before posting I also checked at intodns.com the main domain (myserver) and it was ok, it's still ok. That's what I don't understand, if this one is good, as all others are pointing to it, they should be ok too !

 

Don't deploy core services like DNS with the same hostnames, especially if you are not that familiar with the process. DNS caching can lead to massiv headaches especially while debugging.

Can you describe the steps that you've taken to change out "server1.myserver.com"? Is it still the same IP or a new IP but the same hostname?

 

Well..

I have 2 servers : oldserver since years with IP_ADDRESS_1, working fine with ispconfig, and a new one since 2 days with IP_ADDRESS_2

I installed debian 12 and everything following the perfect server for debian 12 tutorial, everything seemed ok
I created everything on ispconfig's new server to have the same that is on the old one (on the dns settings I have set the new IP address but the same NS as I planned to use it on the new server)
I dumped every DB's and with scp I sent every websites and DB files on the new server (chown with the good web number, etc.)

I went on internetbs.net where all my ND's are registered (they all point to server1.myserver.com except myserver.com that point to IP_ADDRESS_1 which is the principal IP address of the old server) and modified the IP address of myserver.com so it point to IP_ADDRESS_2 (the principal IP address of the new server), hoping that everything works fine, but it didn't

If you need any other informations...

 

Check that the new DNS server is working globally and change all the DNS zones to use the new nameservers - be aware you need to change the NS records themself within the zones managed in your panel aswell as the GLUE records at the registrar.

Wait for the changes to be propergated and check if everything is pointing correctly to the new servers.

 

Hey pyte,

Thx again. If you know any tools that could help me to check if everything works fine with DNS, I take it

I'll check all of this and come back to let you know what was wrong..

 

You can check a few things with tools like https://intodns.com/ or https://mxtoolbox.com or locally with nslookup or dig

 

My signature has link to DNS tutorial, troubleshooting instructions included.

 

Thanks a lot to both of you, pyte & Taleman

I'll let you know what was wrong when everything will be ok