I have the same problem, I get a black screen with "Connection failed". It works with all other browsers (IE, Opera, Chrome, Safari)
On the server (FMS 4.5), logs say : "unknown pageurl http://www.site.com, rejecting connection -"
Meaning well that what Edgar says is correct
This is a very urgend bug.
The amost last reason to use flash player is streaming video.
We are delivering millions of streams a day to millions of user.
Unfortunately there are hundreds of thousands of users with this bad exprience.
When I use firefox10.0.2 and flash player 188.8.131.52 to access http://mytv.tvb.com/live/hdj#page-1, it shows "Failed to connect to the server, please try again". But, it's ok when I use Internet Explorer or Chome. There is no problem in firefox if I used the ealier version flash player.
I'm using Windows 7 with Firefox and Seamonkey with Flash Player 184.108.40.206 and i can play
this video with jwplayer.
When i upgrade to Flash Player 220.127.116.11, error "Stream not found:"
I downgrade Firefox to 8.0 and Seamonkey to 2.5 and i can play this video.
I downgrade Firefox 10.0.2 with Flash Player 18.104.22.168 and i can play this video.
With Google Chrome 17.0.963.56, Opera 11.61 1250, Safari 5.1.2 and Internet Explorer 9.0.8112.16421
and flash player 22.214.171.124 i can play ok this video.
I tested with Mac Os X Lion 10.7.3 and Seamonkey 2.7.2 and Firefox 10.0.2 with
Flash Player 126.96.36.199 and the same error.
The Jwplayer version is 5.9.2128
I downgrade Jwplayer to version 5.2.1151 and the same error success.
Can you test and resolve it?
Thank you guys for posting links. I've been able to reproduce this and will be entering an internal bug on this immediately. Could one of you please open a new bug report on this over at bugbase.adobe.com? Please post back with the URL so that others affected can add their comments and votes.
I'll link the bugs together once that is done.
The bug has already been reported and has quite a growing thread, through it is currently in "ToTest" status with reason "CannotReproduce" - I'm assuming that will change now that you have reproduced the issue. Here's the link to the bug:
Thanks so much, Chris!