There was an error updating the certificate: Error 'Requested host

Help
1

I am receiving this error:

There was an error updating the certificate: Error 'Requested host '14408872.deployments.pbxact.com' does not resolve to 'xxx.xxx.xxx.xxx' (Found 63.227.75.142)' when requesting http://14408872.deployments.pbxact.com//.freepbx-known/8713f9319d562903d425cd904165593e

In the error above, xxx.xxx.xxx.xxx is my current IP address. The IP address it found is a previous IP address of the server (We got a new ISP). It seems like the error is saying that the DDNS address (14408872.deployments.pbxact.com) is trying to direct to the old IP address. But my DDNS settings in system admin and on the Sangoma portal both point to the new IP address, xxx.xxx.xxx.xxx. I tried deleting the old certificate and tried creating a new one (using let’s encrypt) and I received the same error.

Any idea how to fix this?

My domain is: 14408872.deployments.pbxact.com

I ran this command: - Tried to create a new Let’s Encrypt certificate in FreePBX

It produced this output:
There was an error updating the certificate: Error 'Requested host '14408872.deployments.pbxact.com' does not resolve to 'xxx.xxx.xxx.xxx' (Found 63.227.75.142)' when requesting http://14408872.deployments.pbxact.com/.freepbx-known/8713f9319d562903d425cd904165593e

where, xxx.xxx.xxx.xxx is my current IP address of my server. The other IP is an old IP of the server (we changed ISPs)

My web server is (include version):

The operating system my web server runs on is (include version): FreePBX 13 machine (On Centos 6)

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

2

That error message doesn’t come from Let’s Encrypt. People here may know the answer, but you may need to ask on FreePBX’s site.

1 Like
3

Thanks, Mnordhoff. I have posted this on the FreePBX boards as well but have had a response. Just figured I’d try over here as well.

4

I’ve asked on the FreePBX forum and haven’t been able to find an answer. Anyone in here have any idea how to correct this? Or can point me in the right direction on how Let’s encrypt is finding the old IP address?

5

That error message isn’t from Let’s Encrypt. With luck, someone here will be familiar with FreePBX’s software. If not, we won’t be able to help. :sweat:

1 Like
6

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