During activation it for some reason it wants to use port 80 while using port 443 (https). However, port 80 is not reachable.
So I retried, and I get the following popup
Existing Deployment Found!
Deployment xxxxxxxx is currently assigned to this machine and is available for activation.
Again, it wants to use port 80, and won’t activate. So I got an a-ha moment and did this in the CLI
fwconsole sa a xxxxxxxxx
Successful registration so then I head back to the Web GUI, and bam! again.
Existing Deployment Found!
Deployment xxxxxxxx is currently assigned to this machine and is available for activation.
What’s going on with this?
More info. When trying to redo the activation, I see the following popup
We have identified that the admin port has been changed to 80. The wizard will try to automatically redirect to the new port, but if that doesn’t work, click on the ‘Continue’ button to redirect manually.);
I had this problem recently too. The fix for me was to change the ports via the command prompt
in putty get into mysql, then use the asterisk database, then change the lets encrypt port to something other than 80, then change the http port to 80. Once it’s activated you can change the ports back in the sys admin module.
See dicko’s comment at the end of the thread for the proper syntax, the forum strips some of the formatting. The word key needs the single back quote (next to the 1 on the keyboard) around it.