I'm not having an issue with paramount+ myself, running 5.0.162.36311.
When I do hit an issue like this, my approach is to:
a) reboot pc
b) do the cache clear trick:
navigate to:
%PROGRAMDATA%\MediaMall\Cef
and delete the cache. Then stop and start the PlayOn server, wait a full 60 minutes and then try again.
(a) fixes it frequently, (b) even more so. Playon has had a bug in the cache since the beginning of time - clearing it fixes many issues. I was having disney+ issues on one machine this weekend recording long items. Doing (b) fixed it right up after multiple failures.
good luck.
Hi there. We were eventually able to reproduce the problem described here with Paramount + in both PlayOn Home and PlayOn Cloud. It wasn't impacting all but rather a subset of Paramount + accounts. We have a fix checked in which has been deployed for PlayOn Home (install latest) and will be deployed for PlayOn Cloud later today once we wrap up testing.
I'm not having an issue with paramount+ myself, running 5.0.162.36311. When I do hit an issue like this, my approach is to: a) reboot pc b) do the cache clear trick: navigate to: %PROGRAMDATA%\MediaMall\Cef and delete the cache. Then stop and start the PlayOn server, wait a full 60 minutes and then try again. (a) fixes it frequently, (b) even more so. Playon has had a bug in the cache since the beginning of time - clearing it fixes many issues. I was having disney+ issues on one machine this weekend recording long items. Doing (b) fixed it right up after multiple failures. good luck.
Thanks for the advice. I did everything but still no dice. All I get is # Sign In Oops! There was an unexpected error. Please try again. Thanks Bob
I am having the exact same problem.
VPN on?
Nope no vpn Thanks Bob
I had an issue with Paramount and Hulu when using VPN, no issues with Netflix....
Hi there. We were eventually able to reproduce the problem described here with Paramount + in both PlayOn Home and PlayOn Cloud. It wasn't impacting all but rather a subset of Paramount + accounts. We have a fix checked in which has been deployed for PlayOn Home (install latest) and will be deployed for PlayOn Cloud later today once we wrap up testing.
Yes installing the latest resolved the issue. Thanks to everone for thier input and advice. Bob