-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Twitter embeds don't work on production #99
Comments
Oh, mercy! |
Hi @JohnCarter https://twittercommunity.com/t/oembed-responses-are-returns-with-code-404/136813 (April 2020) Lets see if twitter responds |
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. |
No problem @johncarter- ! |
Thanks for such a great package.
I am using Laravel, locally using Laravel Sail and in production using a Laravel Forge provisioned Digital Ocean droplet.
I am running this code:
It seems that Twitter embeds return an empty array every time on production, but work locally.
Does you have any suggestions why that could be?
Thanks again.
The text was updated successfully, but these errors were encountered: