3CX FQDN Blacklisted by Antivirus / SSL Error / SOPHOS / ESET

[Danvarii]

We are getting reports that customers are unable to connect to xxxx.my3cx.xxx since 30 minutes.
They are getting a 'ERR_SSL_PROTOCOL_ERROR' in Chrome / Edge.

Further investigation learns that this is happening on all deviced with a Sophos or ESET anti-virus installed.
Seems like the endpoint protection did a definition update that is marking xxxx.my3cx.xxx as potentially harmfull.

Is 3CX aware of this?

 

[VasilisV_3CX]

Hi @Danvarii,

Can you PM me the FQDN of the client? I don't believe this has anything to do with Sophos or ESET AV's installed on the client's machines that are trying to access the FQDN, at this point.