Answer the question
In order to leave comments, you need to log in
Twitter blocking oEmbed?
The site set the ability to scrape a tweet when posting with a link to Twitter and display it in a frame.
I use https://github.com/oscarotero/Embed/ (and this is just to understand the problem - the problem is not in this library at all).
Everything went well for a year or two.
But at the beginning of the week, I began to notice that Twitter did not give a normal look, and when searching for a problem, I discovered that the IP of my server was tritely blocked.
For example,
From my server I send: lynx https://twitter.com/QuinnyPig/status/1250910042246...
Returns 404
From localhost or any other IP - everything is fine.
Accordingly, I conclude that my "server" IP is blocked personally.
I note that there are no more than 10-20 such embed posts on the site per day.
When searching for a solution to the problem, I did not find anything intelligible about the restriction of oEmbed embeds of tweets.
And why would Twitter do that?
Removed all restrictions from the firewall and fail2ban rules - checked - nothing.
At the same time, other oEmbed inserts (what else to call them), for example, with FB, Instagram, work fine.
Yes, and as I indicated above, the reason is solely in the suspicious blocking of my server IP.
What and how to do?
If the problem is exceeding any limits for such oEmbed posting, then poke your nose - I did not find this in the Twitter help ...
PS: Me, of course. I can use a proxy, etc. means for scrapping, but I'm interested in the essence of the problem - I (the server) is to blame for this or Twitter limits such a thing.
If the latter, then how do the same TJ, VC and similar sites cope.
PSS: Any clarification on the configuration of anything and everything to solve this quest
Thanks in advance for your help and stay healthy.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question