#1

I’m getting this issue too - https://twittercommunity.com/t/oembed-responses-are-returns-with-code-404/136813

things were working fine last week, then all of a sudden every ombed request comes back as a 404. works fine locally and on different servers.

example request that returns a 404:

curl "https://publish.twitter.com/oembed?format=json&url=https://twitter.com/Twitter/status/1494386599781675015?s=20&t=-6WDV3MQQ3P8WDPtgLXwBw"

please help!

1 Like
#2

As of yesterday our servers are also getting 404 on oembed URL’s (US/DigitalOcean) where other machines in Europe and/or other cloud providers are not having issues and return a valid json response.

Any help would be appreciated!

1 Like
#3

Hi there!

Could each of you please provide us with any of the following you are able to share so we can look into it more closely?

  • Request IP
  • User agent
  • Tool you are using to make the request
  • Any specific errors that are being passed back with the 404s

Thanks so much!

Ben
Twitter Eng

3 Likes
#5

And just as happened in the previous topic it started working again an hour ago. I was just testing with

 curl 'https://publish.twitter.com/oembed?url=https%3A%2F%2Ftwitter.com%2FInterior%2Fstatus%2F507185938620219395'

resulting in a 404 page with a nice poodle on our servers for the last 48 hours (+/-)
No other information and/or error message were present in the response and I was making this request from at least 5 different droplets on the Digital Ocean platform in two different regions (all US)

Unfortunately I don’t have timestamps on this but this was before and after :
https://pastebin.com/HP5R7MdA
Mark

1 Like
#6

Yep, it’s working again for us now too.

also from a Digital Ocean droplet (London).

1 Like
#7

Great! Glad to hear it’s working again for everyone. Don’t hesitate to reach out if you have further problems!

Ben

1 Like
#8

Hey there i am still seeing 404’s on my embed and it started yesterday.

  1. Request URL:
    https://cdn.syndication.twimg.com/timeline/profile?callback=__twttr.callbacks.tl_i0_profile_isthi_irfan_old&dnt=false&domain=isthi.xyz&lang=en&screen_name=isthi_irfan&suppress_response_codes=true&t=1829987&tz=GMT%2B1100&with_replies=false and its on my website isthi.xyz

Its on my website

#9

We are also still seeing 404’s on our embed.

Request URL:
https://cdn.syndication.twimg.com/timeline/profile?callback=__twttr.callbacks.tl_i4_profile_ETB_Updates_old&dnt=false&domain=www.energytoolbase.com&lang=en&screen_name=ETB_Updates&suppress_response_codes=true&t=1830010&tweet_limit=5&tz=GMT-0500&with_replies=false

Thanks for your help. Let me know if you need any more information.

1 Like
#10

Same here!

#11

We are receiving a 404 on our embed from a digital ocean droplet as well - Have been since yesterday.

widgets.js:8
GET https://cdn.syndication.twimg.com/timeline/profile?callback=... 

net::ERR_ABORTED 404

EDIT: I am also getting this same error on my local dev environment. Initially I thought it may be a DO IP thing, but seeing as I still get the error on my dev machine…

EDIT2: Seems to be resolved. Will bump if it occurs.

#12

I can confirm I’m also seeing this for the embed timeline. Across multiple sites (even local) and profiles. Strangely enough… this doesn’t seem to affect Twitter’s own publish page.

There’s mentioned of this issue around this time last year:: embedded-timeline-creation-throws-error-requesting-cdn-syndication-twimg-com/149252/14

Failed to load resource: the server responded with a status of 404 ()
#13

@CBallenar Just tested to see if it was also local, and sure enough: I am also receiving the error on my local environment.

#15

Issues seems to be resolved; Will continue to monitor.

1 Like
#16

I’m seeing this resolved here as well. Let’s hope it stays that way! :crossed_fingers:

#17

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.