We are experiencing sproadic issues where our WebSDK implementation fails to load. It appears to be an intermittant certificate error in the connection to an underlying web socket. Doesn’t happen all the time but happens frequently.
Doesn’t happen all the time but happens frequently. Script error recorded in console indicates failure loading wss://zoomscm174rwg.zoom.us/… with a status ERR_CERT_COMMON_NAME_INVALID. Can’t navigate to that URL as it’s wss:// not http:// but when we visit https://zoomscm174rwg.zoom.us/, I do see the certificate does report as invalid - wildcard issued to *.sc.zoom.us, but this resource isn’t part of the sc.zoom.us subdomain.
Not sure how to reproduce, as often times it will work again after closing the browser/relaunching. Seems like WebSDK may be round-robining different endpoints into the clients, only some of which fail.
To Reproduce(If applicable)
We can’t reproduce reliably. Bad certificate can be viewed here - https://zoomscm174rwg.zoom.us/
Smartphone (please complete the following information):
- Browser: Chome v.81