Description of issue:
Our Twitter previews stopped working on some odysee dot com links. They work fine everywhere else.
URL affected (must be public):
Could not post url for some reason - replace dot with .:
https:// odysee dot com/@ChesatohiCryptoCoffee:2/CC366-StakeFi-Reward-with-DeFi:d
Troubleshooting steps attempted [note that we will not prioritise posts unless there is evidence of following the troubleshooting guides]:
Tried these, any additional information is appreciated.
Sorry for some of the duplicate posts from our CDN partner, we were concerned about the trouble posting.
Here’s an example of a link that works fine:
https:// odysee . com/@AwakenWithJP:9/should-biden-resign-(even-though-he-did:c
Here’s a better example of a broken one which uses a CDN to host the thumb:
Example URL: odysee . com /@bannertest:4/testtttterere:b
Card Image URL: lbry2. vanwanet.
com/speech/dd08e77d9dbb0481:d.jpg
Hello? Can we please get some assistance? Our website sees 33M last month
1 Like
Bump
Please, we are getting lots of complaints from our users and creators about this. These links work everywhere outside of twitter.
2 Likes
I can’t figure this out either.
It’s really weird that it does everything correct except the thumbnail.
1 Like
The only thing i can think of, the page has:
<meta name="twitter:image" content="https://thumbnails.lbry.com/ghqHxWCQESk"/>
and i guess Twitterbot doesn’t like it that the url doesn’t end in .jpg or .jpeg?
It’s very temperamental - it may also be failing because it’s a different domain? It also doesn’t seem to like redirects in the images either - like https://spee.ch/1/32c74bcb2b68e61e.png above, it redirects to https://lbry2.vanwanet.com/speech/32c74bcb2b68e61e:1.png - the only way i got it to work in the past was to directly hotlink a statically served jpg file.
[edit: I think i made a mistake, https://thumbnails.lbry.com/ghqHxWCQESk was the working one? this one fails, right? https://lbry2.vanwanet.com/speech/dd08e77d9dbb0481:d.jpg in that case maybe the issue is with the : in the URL?]
1 Like
Thanks as always, Igor.
I was thinking that about the : too. I know it used to be used for a bunch of weird things. But another page works with it present, and on a different domain (with no extension in the url path).
Def weird
1 Like
Bump. Please, anyone? This is negatively affecting our content creators and using sharing links!
1 Like
I am seeing HTTP timeouts on lbry2.vanwanet.com which might indicate that it is blocking the Twitter IP ranges, or the Twitterbot crawler.
Thank you for the reply Andy! Who would we get in contact with to resolve this? Vanwatch is our CDN and not really sure why it would be blocked. I know they’ve done some upgrades in the last few months too, so maybe something related to that.
Anyway you can DM or point us to info how to get this resolved?
I’d suggest confirming with the CDN that they do not block the Twitterbot User-Agent, or the Twitter outgoing IP ranges (which are documented on this page). That’s all I can currently think of as a potential reason for the timeouts, other than routing issues.
I am the CEO of VanwaTech - we are doing the CDN, I am currently looking into this
We don’t block the twitter user agent that I am aware of, nor do we actively block twitter IP addresses
I am wondering if the colon could indeed be the cause
We also use IPv6, so I am not sure if twitterbot supports IPv6 or not
See replies above from our CDN provider. Is IPv6 supported?
I checked an example with : in URL , and it’s fine: test colon thumb -
“og:image”:“https://s3.amazonaws.com/thumbnails.lbry.com/test:1.png”
1 Like
Bump? Kind of sad to not get support from such a prominent product in th space.
Apologies - I meant to follow-up on Friday. I did confirm that IPv6 is supported by the cards crawler.
We have no choice but to change our service for this, but it would be good to understand what’s actually going on.
2 Likes
Man… gonna be straight with you - I’m not twitter and i’m just spitballing - but my guess would be that it’s your host - not anything you’re doing.
Vanwatech hosts a lot of openly Nazi, Q conspiracy and some other very dodgy borderline porn shite on 8kun, https://www.bloomberg.com/news/features/2021-04-14/qanon-daily-stormer-far-right-have-been-kept-online-by-nick-lim-s-vanwatech so i wouldn’t be surprised if the reason why images are failing to load from your CDN is because your CDN is dodgy.
That may be the case, but it would be nice if Twitter were just upfront about it.
2 Likes
system
Closed
#20
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
