Pipelight

Error N8109 loading a videos in Netflix with chrome 31

Asked by William

I click on a video and it loads but instead of the the red screen with the progress bar it gives me a black screen with glowing circle in a loading pattern for mayb 30-45 seconds before the message:
Unknown Error
An unknown error has occurred.

Error Code:N8109

I have Chrome UA Spoofer loaded and copied the windows chrome tag line from the firefox user-agent. Without some idea on how to get more information its not much help unless you have the netflix error code book. I tried seeing if there was any option for pluginloader.exe for debugging but there doesn't seem to be any help. I searched the ./wine-pipelight and /usr/share/pipelight and don't see any session logs or such. I only found the configure file with with to big DNS looking number.

Question information

Language:
English Edit question
Status:
Solved
For:
Pipelight Edit question
Assignee:
No assignee Edit question
Solved by:
Sebastian Lackner
Solved:
Last query:
Last reply:
Revision history for this message
Best Sebastian Lackner (slackner) said : 		#1

Hi,

at first you should ensure that you've installed the latest version (we had some problems with an update recently):

sudo apt-get update
sudo apt-get upgrade

After this: Your problem is most probably similar to this one: https://bugs.launchpad.net/pipelight/+bug/1213672
Just set the user-agent string to the following one which is known to work and it should be fixed:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1

You can check your user-agent using the diagnostic page: http://fds-team.de/pipelight

Sebastian

Revision history for this message
William (feiwuzei) said : 		#2

Yeah the Mozilla tag line worked. But I have to say the reloading, like if you skip about in the video, in chrome is extremely slow compared to Firefox.

I did search for n8109 before it it didn't come up. That is what I hate about most search engines.

Revision history for this message
William (feiwuzei) said : 		#3

Thanks Sebastian Lackner, that solved my question.