3CX Client Update Fails to negotiate SSL/TLS

[Thomas Miller]

Hello All -

I switched my users from Fonality to 3CX a couple of days ago. During testing, our PCI scan showed TLS 1.0 was enabled on the management interface. As this is now a failing condition, I disabled TLS 1.0 and 1.1 in the nginx.conf file and restarted nginx. Everything worked so I thought all was well. However, after bring users onboard, it now seems that without TLS 1.0 enabled, the Windows client cannot update. If I re-enable TLS 1.0, it works. Is there a fix for this that would allow me to disable the weak ciphers and still have the clients update?

 

[YiannisH_3CX]

Hello @Thomas Miller

Please note that this is discussed in another thread. You can find it here: https://www.3cx.com/community/threads/error-updating-3cx-client.53457/
The last 3-4 replies will be of interest to you

 

[Thomas Miller]

Thank you. I noticed a similar answer in another thread and was able to fix the issue by re-enabling TLS 1.0 and 1.1, allowing the update, then disabling. From the thread I saw, this will be the last time we will have to do this.

 

[LeonidasG_3CX]

Thank you. I noticed a similar answer in another thread and was able to fix the issue by re-enabling TLS 1.0 and 1.1, allowing the update, then disabling. From the thread I saw, this will be the last time we will have to do this.

Exactly.