Player Card bug

[OMGUrOnline]

Yes, ing… been there and done that. As stated before, the Player cards worked perfectly for almost a year (even with the F rating)…

It DOES seem to matter if it’s posted SSL vs non-SSL (the links I provided above only prove that).

http://omgtap.co/userfiles/10000/10001/blogs/1427358593_Just_A_Song/ - WORKS
https://omgtap.co/userfiles/10000/10001/blogs/1427358593_Just_A_Song/ - DOES NOT WORK

This is an example of posting the URL in HTTP vs HTTPS and it WORKING vs NOT WORKING.

Thanks!
Greg

[TeveoStreaming]

Hey, Greg

I see what you mean by works vs doesn’t work. But using the card validator i’m getting an error for your HTTPS URL, specifically: “ERROR: Fetching the page failed because connection is refused.” without solving this issue your card will simply not render in HTTPS.

I had that very same bug 2 days ago with my HTTPS URLs, and just like you, my cards were working fine for more than a year. It seems Twitter made some changes and is getting stricter with the SSL validation now.

[OMGUrOnline]

Yes, Teveo, there are a handful of people I have seen that the Card Validator doesn’t work on - my site included. If Twitter is making changes and getting stricter with their SSL Validation, they probably should post some information on what to do about it.

I’ve read that they just started whitelisting all cards except for the Player Card (which still needs validated)… My Player cards are validated. Everything worked perfectly until March 6th for me - then the validator started refusing the connection, and the media on the player cards stopped showing up.

Absolutely no changes on my end. I’m just hoping someone at Twitter might see these posts, because the Player Card feature is why I started using Twitter and without that feature, i’m probably history…

Thanks!
Greg

[tarader]

Same problem here, and my domain has an A SSL rating, so I don’t think the problem comes from that side

[ing_jk]

We are currently in panic mode because of this. We even bought a new domain and applied again for Player Card, but it was rejected because "Your card loads on iOS and Android, but not on desktop"

Our cards works on desktops, obviously, but Flash Player is required.

[OMGUrOnline]

Update:

My server, omgtap.co, now has a “A” rating on the SSL via https://www.ssllabs.com/ssltest/analyze.html?d=omgtap.co and the player cards and validation still do not work on SSL but work on non-SSL.

Greg

[Sergiosarpe]

Adding to the investigation I’ve just found out there are a lot of sites without this restriction in their Player Cards, not only the big sites like Youtube, Livestream, Ustream or the others already mentioned. One of this ‘small’ sites is heyheyapp.com

Tweeting https://heyheyapp.com/p/gLD.MT?twembed will create a player without the infamous sandbox attribute.

Is there any twitter staff in twittercommunity.com who can answer why we are getting the restriction and others aren’t?

[dev_flux_uk]

Hi there,

We’re also experiencing the same problem, everything working fine until about a week ago and now the player card just renders a black space instead of the player - but the validator still loads just fine. Our content is also distributed via a secure CDN so the certificate should have a pretty high rating.

[Tim_LB]

Any Twitter staff around? This is getting pretty urgent… any way to avoid having the sandbox tags added automatically? Our player has been whitelisted for a while now, and we have urgent events that requires a working Twittercard coming in a few days…

Thanks!

[jbulava]

Hi everyone,

I wanted to let you all know that I have made the Cards team aware of this issue and they will investigate. A followup will be posted as soon as I know more.

Related post: Video Card
Tracking internally as PREL-12914

[OMGUrOnline]

Tim,

I found a temporary workaround for this issue on my site. It might work for you if you have some urgent posts coming up.

If I post a non-SSL url to Twitter, the cards work fine. I haven’t changed anything with the Twitter Player Card meta tags - they still point to secure links. I did have to disable the automatic redirect on my website so that it doesn’t redirect everything back to SSL.

It’s a workaround, but it works on my end… Maybe it will help someone else!

https://omgtap.co/userfiles/10000/10001/blogs/1427358593_Just_A_Song/ - doesn’t produce a card when posted - try tweeting this url within Twitter.

http://omgtap.co/userfiles/10000/10001/blogs/1427358593_Just_A_Song/ - WORKS when posting - try tweeting this url within Twitter.

Strange, but it’s a temporary fix. Hope this helps someone! This problem has been going on for a month for me.

Greg

[OMGUrOnline]

jbulava,

thank you! someone from Twitter does exist in the forums. it seems like we have been talking to a wall for weeks!

Greg

[jbulava]

It’s true, we are in the forums whenever possible! Apologies for your Player Card frustrations while we sort things out.

[Tim_LB]

Thanks Greg, I’ll look into this, but hopefully jbulava will have things sorted out fast?

Thanks for taking care of the issue btw!
Tim

[jbulava]

The Cards team identified the issue and it has been resolved. I tested a couple of URLs, but please confirm that your Player Cards are now working.

[Tim_LB]

Thanks a lot! Looks back to normal: perfect

[OMGUrOnline]

Nope, my cards are not working (and not validating) just like before…

https://omgtap.co/userfiles/10000/10001/blogs/1427358593_Just_A_Song/

Greg

[jbulava]

The issue in the initial post concerning the sandbox attribute was resolved.

@OMGUrOnline, your issue relating to a connection refusal will be passed onto the Cards team as well; it is unrelated to the first post. I will be replying to and referencing the following thread: Connection refused when fetching a summary card

[ing_jk]

I can confirm the issue is now resolved, and also would like to thank @jbulava, @romainhuet and the Cards team for their invaluable help.

¡GRACIAS!

[jbulava]