Twitter embeds don't work on production about embera HOT 5 CLOSED

No problem @johncarter- !
Thanks for the feedback, Im closing this issue. 👍

from embera.

Oh, mercy!

oscarotero/Embed#518 (comment)

from embera.

Hi @JohnCarter
Yes, Indeed there seems to be a problem with some hosting providers. I had a report coming from German servers having the same problem adn while doing the debug we found this instances where something similar happened:

https://twittercommunity.com/t/oembed-responses-are-returns-with-code-404/136813 (April 2020)
https://twittercommunity.com/t/oembed-404/167966 (März 2022)
https://twittercommunity.com/t/issue-with-twitter-oembed-api-when-accessed-from-digitalocean-droplets/194215 (May 2023)

Lets see if twitter responds

from embera.

There seems to be a solution to this problem:

Given the ip address ranges described here: https://developer.twitter.com/en/blog/product-news/2022/updated-source-ip-address-range

You need to allow all TCP connections from those IP ranges.

https://300m.com/security/twitter-oembed-broken-on-digitalocean/

Let me know if this works for you.

from embera.

I can confirm the following works:

1. Go to Digital Ocean control panel > Networking > Firewalls (tab) > Create Firewall

2. Add the following rules:
   

3. Assign that rule to your Droplet.

4. Profit 💷

Thanks again for the package and prompt response, it's highly appreciated.

from embera.