video not displaying

Asked by William Cody Laeder

I've installed pipelight, I can see it in my about:addons within firefox.

I can see the bouncing balls sample (http://bubblemark.com/silverlight2.html). But this example (http://www.iis.net/media/experiencesmoothstreaming) gives me nothing. I've changed my client string to be chrome/windows instead of my native firefox/linux to avoid issuses.

Also on netflix's website I receive the protocol not idenfied nflx error

Question information

Language:
English Edit question
Status:
Solved
For:
Pipelight Edit question
Assignee:
No assignee Edit question
Solved by:
William Cody Laeder
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
Michael Müller (mqchael) said :
#1

This error is most probably related to a bad user agent switcher. There are several ways for a site to check for a user agent, but not all browser addons patch every possibility. Please try the ones mentioned in the faq https://answers.launchpad.net/pipelight/+faq/2351 which are known to work. This should fix your problem.

 In order to check if your user agent is working properly you can also use the following two sites you check the identity:
- http://useragentstring.com/
- http://www.javascriptkit.com/javatutors/navigator.shtml

Especially the second test is important. You can find the result under the table ("Let's see exactly what these properties reveal of the browser you're currently using:").

Revision history for this message
William Cody Laeder (codylaeder-e) said :
#2

My agent string appears working

Here is a link to a screenshot using the first tool you linked http://i.imgur.com/XqxJJ1G.png

Revision history for this message
Sebastian Lackner (slackner) said :
#3

Hi,

The url http://bubblemark.com/silverlight2.html works without user agent check,
but http://www.iis.net/media/experiencesmoothstreaming requires having a user agent switcher that also fakes the JavaScript user agent - otherwise it will not show anything or hang at 100%.

You can verify the JavaScript user agent via the second link ( http://www.javascriptkit.com/javatutors/navigator.shtml ) Michael Müller wrote. Please note that the JavaScript user agent might differ from the regular one.

This page shows something like:
------------------
Let's see exactly what these properties reveal of the browser you're currently using:

appCodeName: Mozilla
appName: Netscape
appVersion: 5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36
userAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36
platform: Linux x86_64
---------------------

If these values (requested by Silverlight) contain something unusual it will refuse to work properly.

When unsure if your user agent switcher is working properly just try one of the recommended user agent switchers and choose an identity that already has been verified to work. I'm not sure if this is the case with Google Chrome.

Sebastian

Revision history for this message
William Cody Laeder (codylaeder-e) said :
#4

Thanks Sebastian Lackner, that solved my question.

Revision history for this message
William Cody Laeder (codylaeder-e) said :
#5

Well I start at the loading screen then I get the N8109 error...

Revision history for this message
Sebastian Lackner (slackner) said :
#6

Hi,

Error N8109 is also related to a wrong user agent - some people have already confirmed that this problem disappears by setting an appropriate user agent string.

See for example these bug reports:

Netflix error N8109 when using Firefox
https://bugs.launchpad.net/pipelight/+bug/1213584

Error 8109 when watching programme
https://bugs.launchpad.net/pipelight/+bug/1213672

In both cases it was related to a wrong user agent.

The following configuration has already been confirmed to work, probably you should try this one, too:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1

Sebastian

Revision history for this message
William Cody Laeder (codylaeder-e) said :
#7

I recieve it in both firefox and chrome

Revision history for this message
William Cody Laeder (codylaeder-e) said :
#8

updated user agent string now it works