Forum Discussion
Is there a workaround for Channels that do not directly control the streaming servers? The suggested roUrlTransfer.EnablePeerVerification(False) does not apply to requests sent by the Video Player
- OddScott6 years agoRoku Guru
After some further experimentation, it seems that my problem was caused, at least in part, by an SSL certificate purchased last year from Namecheap.com and configured into the CDN. After installing a new SSL certificate purchased from GoDaddy.com today, the problem is resolved!
- RokuTomC6 years agoCommunity Moderator
Unfortunately, your only option is to add this API call to your channel source. If this isn't possible or isn't resolving your issue, then the only remaining option is to wait until Roku OS 9.3.0 v4170 is fully deployed. 4170 includes a ca-cert bundle update.
Note also that any end-user on a set-top box or streaming stick can currently manually update to 9.3.0v4170. Roku TVs will fast-follow with a patch.
- tifroz6 years agoStreaming Star
Sorry if I am being dense, but I think you are suggesting that the httpAgent of a VideoNode can be configured to work around the expired certificate? If so, can you provide an example of the API call you are referring to?
My current understanding is that the EnablePeerVerification() API is only available to roTransferUrl objects, which do not affect VideoNode requests to streaming servers. Correct me if I am wrong here?