Currently having an issue with Polycom VVX devices being unable to connect to provisioning URL. This was working up till Wednesday morning but today fails trying to connect to provisioning URL with
13:58:10.061 192.168.0.56 local0.error 0420135809|copy |4|00|SSL_connect error Peer certificate cannot be authenticated with known CA certificates.SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed
This also means that provisioned devices show as offline as they cannot connect to Tenant. Is this a known issue?
Hello @JohnG0703 ,
welcome back to the Poly community.
I suggest to bookmark or subscribe to https://status.plcm.vc/
There was an issue earlier today. I suggest to try again.
Best Regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------Thanks Steffen
I had subscribed to the status updates but only showed System Maintenance for yesterday morning.
Provisioned device is now showing as online in portal but still seeing SSL error in device logs.
New device being provisioned shows same SSL error but will not connect and doesn't show up in Inventory.
Currently trying some additional testing.
Thanks
John
Same here. All the already configurated phone in lens (+400) are not able to connect to lens since Wednesday around 16:30 EST.
We a currently unable to provision new phone. All connexion to poly lens provisionning URL give us a TCP RESET FROM CLIENT.
If we try to open your provisonning URL in a browser (xxxxx be our ID: https://txxxxx.deviceprovisioning.dm.lens.poly.com/), we receive a "504 Gateway Time-out".
Is there a outage from some tenant?
Hello @Benjamin D. and @JohnG0703
the issue should be fixed since yesterday evening. Please work with our support team if you still see an issue.
Best Regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------Hi Steffen
All working this morning. Going by update it was fixed around 05:40 GMT.
Thanks