403 on oEmbed from a hosted server

[MrFollies]

I'm trying to implement automatic embedding of spotify tracks/albums etc in a blog site.

But it is being blocked.
When I try this at home:

curl -v "https://open.spotify.com/episode/7makk4oTQel546B0PZlDM5"

I get the JSON returned just fine.    It includes a JSON object containing the html to make this:
https://open.spotify.com/episode/7makk4oTQel546B0PZlDM5

If I try it from an amazon aws instance, I get a 403 from spotify.

Should I be trying to get the client to do the embed request?   I suspect that will fail with XSS issues.

Does spotify dislike websites doing embed lookups?

Info and example URL taken from here:
https://developer.spotify.com/documentation/embeds/references/oembed-api/#/operations/oembed

[MrFollies]

.

[boczka]

We're experiencing the same issue on our app hosted on Heroku (which uses AWS infrastructure, if I'm not mistaken). Doing the same requests from my local machine works as expected.

[Nick190]

Getting the same issue for our oEmbed plugin (hosted on AWS Lambda). Works fine locally.

[fzhan]

Same 403 error here.

Hosted on GCP asia-east1.

Works fine locally too.

[faceinjarbydoor]

I have a Discourse instance running on a Vultr cloud server and am experiencing the same issue. Pasting a Spotify link into a post used to generate a nice preview; now the attempt to generate a preview yields 403 Forbidden. I'd love to find out why this suddenly stopped working.

[kopiro91 · Accepted solution]

Hello, the issue has been fixed on our end.
I can confirm that you should get the correct response with HTTP 200.

[MrFollies]

Can confirm the problem is fixed now...