Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

embed codes are not working for either cloud-hosted or self-hosted pages


On my page http://egbn.org/JWP6test/index.html the code executes all around the player, but the player doesn't appear at all. The current iteration is using the cloud-hosted embed code. The self-hosted page is located at http://egbn.org/JWP6test/jplayer.html

James

20 Community Answers

egbn.org

User  
0 rated :

BTW, the embed codes were copied directly from the Publish Wizard - Get Embed Code page. The previous Configure Your Player page show an actively working cloud-hosted JWPlayer using my video, image and title.

Why doesn't the embed code work too?

Andrew

JW Player Support Agent  
0 rated :

When I copy this to my localhost, everything seems to work properly. Can you try changing your meta charset to meta charset=‘UTF-16’ here? Or try removing it all together.

egbn.org

User  
0 rated :

OK Andrew,
I removed the charset='UTF-8' completely, and still the player does not appear. I tried from a different computer on the same intranet, with the same results. Then I switched to my tablet (on wifi) and changed to xfinitywifi ( I'm in their footprint and have an account with Comcast). The first time I attempted with the tablet, the placeholder for the player appeared between ...Loading... and Page Code, but no player appeared.

I thought it might be my local network so I shutdown my computer, turned off my router, disconnected the switch, and unplugged my modem (reset everything). I came back up in 3 minutes, and STILL NO PLAYER!

What else could be my problem?

James

egbn.org

User  
0 rated :

When I attempt to load jplayer.html (the self-hosted code) with the tablet using the default browser (while on xfinitywifi), the placeholder for the player appeared between ...Loading... and Page Code, but no player appears. I've waited up to 5 min. for the player to load each time, but no player loads. The file index.html (containing the cloud-hosted code) does not show any player or placeholder for the player.
When using the tablet on xfinitywifi, the self-hosted code does NOT work on CHROME (regular or Beta) or Firefox.

egbn.org

User  
0 rated :

No sooner than I tried using IE (which I NEVER use for anything) when both cloud-hosted and self-hosted version worked perfectly! With and without the '<!DOCTYPE html> tag!

Andrew

JW Player Support Agent  
0 rated :

Ah! Is everything working then?

egbn.org

User  
0 rated :

It only works in IE11. I've even tried from a different computer in a different physical location (at my daughter's house-different network, modem, provider), both wireless (wifi & 4GLTE) and wired. From Chrome & Firefox on desktop, phone and tablet, it does NOT work.

dykesje

User  
0 rated :

Andrew,

I ran my code through W3C Validator, cleaned it up and the URL is http://egbn.org/JWP6test/djeplayer.html

I even tested the javascript playlist code!
My problem is that even though this page displays properly in IE11, I still can't get it to work in any other browser I've used:
Chrome desktop, Firefox desktop, Chrome tablet (Samsung GT-N8013), Firefox tablet, or Chrome phone (Moto X).
Neither the player or a placeholder for the player appears on the aforementioned browsers. But a placeholder for the player appears on the Firefox phone browser!

I don't understand what's wrong--Help! :-)

Andrew

JW Player Support Agent  
0 rated :

I’m getting the following error here:
The requested URL /JWP6test/djeplayer.html was not found on this server.

Is this still set up?

dykesje

User  
0 rated :

Yes Andrew,
The self-hosted page is at egbn.org/JWP6test/djeplayer.html and the cloud-hosted page is .../jplayer.html

dykesje

User  
0 rated :

Sorry Andrew,
I switched nameservers last night. will switch back until we get this right.
James

dykesje

User  
0 rated :

nameserver propagation should be finished by 2:45pm your time.

dykesje

User  
0 rated :

try using www.egbn.org/... that worked for me just now.

James

MisterNeutron

User  
0 rated :

I don't have an answer to this one, but just wanted to chime in. I've been staring at this poster's page code, and poking around with the developer tools in my browser, and can't for the life of me figure out why the player isn't working on these pages. Biggest mystery I've seen in long time. I keep getting the feeling I'm missing something stupid and simple, but I just can't find it!

Andrew

JW Player Support Agent  
0 rated :

I’ve tried messing with this some more. Again, the exact same code works just fine for me on my localhost, so my guess is that there is some sort of server configuration issue. If you try using our cloudhosted player from your account page here:
https://account.jwplayer.com/#/account

Are you also seeing the same problem?

dykesje

User  
0 rated :

I am seeing the same problem with the cloudhosted player using my coded page which can be found at .../jplayer.html

dykesje

User  
0 rated :

I thought it was possibly a server/hosting problem as well, which is why I had switched name servers last night. I hadn't copied the code yet when you tested the new files, so I changed the name servers back.
The same problem with inability to run on other browsers than IE11 occurs whether the code calls out the cloud-hosted video or self-hosted video. Even when I have everything on my localhost (all files on my hard disk, same directory, using self-hosted code) it will not run from Chrome or Firefox.

dykesje

User  
0 rated :

Problem SOLVED!!

HTML files were being written out as TYPE=unicode by default.
I switched the TYPE to txt and -- Voila!

I can now see my web pages on ALL devices - IE11, Chrome & Firefox (desktop, tablet and phone).

MisterNeutron

User  
0 rated :

Thanks for posting back about this! It was really puzzling me, and I never thought to look at the MIME type of the HTML itself - it's usually a problem of the MIME type on the MP4, so that's what we focus on.

Andrew

JW Player Support Agent  
0 rated :

Glad it’s working! Definitely a first on my end. :)

This question has received the maximum number of answers.