Skip to content
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.

Sign up for GitHub

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

Jump to bottom

403 on oEmbed endpoint via pressable servers #256

Open
tristan-misinc opened this issue Sep 20, 2023 · 4 comments
Open

403 on oEmbed endpoint via pressable servers #256

tristan-misinc opened this issue Sep 20, 2023 · 4 comments

Comments

@tristan-misinc
Copy link

We had this issue previously and it was widespread - was getting a 403 via server calls (cURL via wordpress integration on pressable) and a 404 when trying to access with my browser. This was in early July and was resolved eventually with zero communication on what was going on, why, etc from anyone (both support tickets and github issues).

Again today, the cURL call from our wordpress integration is returning a 403. This time around, I'm able to pull the oEmbed with a browser - same exact url we're calling with cURL.

I'll file a support ticket as well, but this is really frustrating for my clients who depend on SoundCloud to actually deliver their PAID content via their PAID account, not block their content for days on end at random for no apparent reason only to re-enable access without saying a word. I wont be surprised if they move back to brightcove at this point :(
@vinmassaro
Copy link

We are seeing this as well, (cURL via Drupal Soundcloud Field module). This response is being returned:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>403 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: 7GHXB30gC0T6LKW9-Q55MBFYbkzi2EW7SE3M256i3N2M283C853lyw==
</PRE>
<ADDRESS>
</ADDRESS>
</BODY></HTML>

@incorporAI
Copy link

Same here on Joomla integrations

@GabrielMartinsCarossi
Copy link

Same here, getting 403.

I filed a ticket 9 days ago and still got no reply.

@jvandenaardweg
Copy link

jvandenaardweg commented Sep 29, 2023 •
edited

Same issue here since a few days on embeds using a simple PHP script on a PHP forum of mine.

Some details:

array(10) { 
    [0]=> string(22) "HTTP/1.1 403 Forbidden" 
    [1]=> string(18) "Server: CloudFront" 
    [2]=> string(35) "Date: Fri, 29 Sep 2023 12:21:59 GMT" 
    [3]=> string(23) "Content-Type: text/html" 
    [4]=> string(19) "Content-Length: 919" 
    [5]=> string(17) "Connection: close" 
    [6]=> string(30) "X-Cache: Error from cloudfront" 
    [7]=> string(69) "Via: 1.1 1a713b47fe9d05824094426fde008b1e.cloudfront.net (CloudFront)" 
    [8]=> string(22) "X-Amz-Cf-Pop: ORD56-P3" 
    [9]=> string(69) "X-Amz-Cf-Id: PB6WOsf7KLo795GhxFiqS9tUJqZ6DSUQn0SDL48532QOpckPdGf34g==" 
}

Accessing the URL in the browser that returns the oEmbed works ok. So maybe some services got blocked?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@vinmassaro @jvandenaardweg @tristan-misinc @GabrielMartinsCarossi @incorporAI