You are not logged in.
Pages: 1
I just now finished installing pipelight and all the needed dependencies, and the ball test for silverlight works without problem, but when I go to watch netflix, it gets to the loading screen and hangs on 4% loaded, doesn't go any farther. Does anyone know of a possible fix to this? I would prefer to use pipelight over netflix desktop because I like doing other things on my desktop while watching netflix, and I can't do that with netflix desktop because it's fullscreen. someone help!
Offline
I ended up installing netflix-desktop, and it does the same thing, hanging at 4%, then it comes up with
Whoops, something went wrong...
Internet Connection Problem
An Internet or home network connection problem is preventing
playback. Please check your Internet connection and try
again.
If the problem persists, please call Netflix
Error Code N8102-106
Offline
Hi Starscrye,
i'm very sorry, we already had two other users with exactly the same "4% bug" (different distributions!), but so far we don't know any solution for this yet. As it doesn't affect that much users, I assume that there is something configured a bit different, which causes these issues, but we haven't found out what exactly.
I would recommend to check the following things, but not sure if they're causing the issues:
Is your PC clock and time zone configured correctly? As far as I know netflix checks this, and doesn't work with a wrong one.
Do you have some kind of unusual network setup, for example only IPv6 available? If possible try to connect your PC with a different internet connection, and check if this makes a difference.
It could be possible that your system certificates (/etc/ssl/certs/) are not up-to-date. Unfortunately I don't know how they are managed on Archlinux, so probably someone else can give a hint how to check that or update them, if thats possible.
If none of these ideas helps, just report back and we can probably give some additional advices.
Sebastian
Last edited by slackner (2013-11-05 23:15:24)
Offline
Hi Starscrye,
I just wanted to report that the problem seems to be solved now in one of these two cases. As it turned out it was just a DNS problem, probably caused by the Internet provider.
To check if its the same issue in your case just try to access the following page:
https://cbp-us.nccp.netflix.com/
You should get some kind of output, like this:
<status>
<status_code>404</status_code>
<message>Not a valid route /</message>
</status>but no certificate warnings and not that the connection timed out (which was the case for this user).
By switching to googles DNS server (I'm sure you'll find some instructions how to do that on the Internet, or ask me when unsure) the problem was solved. If you've a similar problem I would recommend to try that too.
Sebastian
Last edited by slackner (2013-11-06 01:52:36)
Offline
Pages: 1