Solved SSL certificate renewal failed

[baseuser121]

Hi All,

Our phone system on dedicated windows 10 pc, and its not renewing the SSL. I keep getting failed notification.

Currently 3cx is on

Version Number

16.0.16

Any help is appreciated

 

[Saqqara]

you need to upgrade to v18 ,

backup 3cx with fqdn and license. Move this backup to a folder locally, or outside of 3cx folders.
uninstall 3cx
reboot pc
install 3cx, and select restore from backup during the installation procedure


https://www.3cx.com/docs/manual/phone-system-installation-windows/

 

[baseuser121]

I thought of doing that but I am unable to get v18 for windows. They have removed the link from my customer portal for everyone

 

[baseuser121]

 

[Marconi]

I was having the same problem with my 3CX v16 installation (v16.0.8.9) and installing the update to v16.0.8.16 fixed the problem.

You show a straight v16.0.16 not v16.0.8.16. Is that just a typo?

 

[NickD_3CX]

Hi @baseuser121 ,

We have recently updated the Customer Portal and from what I see in the screenshot, you are seeing the old version of it.

Try to explicitly log out of the Customer Portal, then clear your browser cache, or even try to use an Incognito Window.
The find your license key, click on it, press "Install" and you should get the option to press "Self-Managed" and download it from there:


If you have any trouble let us know.

 

[abhi@businessbroadbanddea]

Thank you

Hi @baseuser121 ,

We have recently updated the Customer Portal and from what I see in the screenshot, you are seeing the old version of it.

Try to explicitly log out of the Customer Portal, then clear your browser cache, or even try to use an Incognito Window.
The find your license key, click on it, press "Install" and you should get the option to press "Self-Managed" and download it from there:
View attachment 30069

If you have any trouble let us know.

Thank you. This has now worked.

 

[abhi@businessbroadbanddea]

I was having the same problem with my 3CX v16 installation (v16.0.8.9) and installing the update to v16.0.8.16 fixed the problem.

You show a straight v16.0.16 not v16.0.8.16. Is that just a typo?

Yes you are right. After the V16.0.8.16 it automatically fixed the issue., Thank you

 

[abhi@businessbroadbanddea]

This issue has now been resolved. Thank you everyone