Why in the world did it work at the time when I created that certificate but it doesn’t work to update it now? I have not changed anything with the configuration of FreePBX ever since I created that certificate.
My URL works perfectly fine and it is a dns service from google. Same exact scenario works in FreePBX 13 using the same dns service. I was just able to update the certificate in that instance.
The token is generated on your pbx and then sent to the mirror server and the mirror server then checks if your pbx really has that token. So if the tokens doesn’t match that means something else is at that url not your pbx
Why did it work out of the box last time and for some magic reason it’s sending a wrong token now? Who told it to send a different token this time? Is FreePBX changing configs on its own or something? I just don’t understand why such a long term supported product has these silly issues still.
Where should I check? I haven’t changed anything with my domain name or IP address. As soon as I installed FreePBX 14 I installed a lets Encrypt certificate, all went well. Did say anything like what it says now.
Hey. I was having the exact same issue. The problem was, that I modified /etc/httpd/conf.d/freepbx.conf to redirect all port 80 traffic to 443. You can either add an exception for .freepbx-known or remove that redirect.