Soundcloud API returns 504 #263

kichkruk · 2023-10-11T08:07:39Z

kichkruk
Oct 11, 2023

Hello!
I'm experiencing an issue when I'm trying to reach API from a server in the Hetzner cloud, I'm getting the following 504 from CloudFront:

curl -X 'GET'   api.soundcloud.com/me   -H 'accept: application/json; charset=utf-8'   -H 'Bearer 1-XXXXXX-55012225-vgvhvjhbhjbjh' -vvvi --proto-default https
Note: Unnecessary use of -X or --request, GET is already inferred.
*   Trying 18.165.140.100:443...
* Connected to api.soundcloud.com (18.165.140.100) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: CN=*.soundcloud.com
*  start date: Jan 24 10:57:15 2023 GMT
*  expire date: Feb 25 10:57:14 2024 GMT
*  subjectAltName: host "api.soundcloud.com" matched cert's "*.soundcloud.com"
*  issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign GCC R3 DV TLS CA 2020
*  SSL certificate verify ok.
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET /me HTTP/1.1
> Host: api.soundcloud.com
> User-Agent: curl/7.81.0
> accept: application/json; charset=utf-8
> Authorization: Bearer 1-XXXXXX-55012225-vgvhvjhbhjbjh
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 504 Gateway Time-out
HTTP/1.1 504 Gateway Time-out
< Content-Type: text/html
Content-Type: text/html
< Content-Length: 1033
Content-Length: 1033
< Connection: keep-alive
Connection: keep-alive
< Server: CloudFront
Server: CloudFront
< Date: Wed, 11 Oct 2023 08:05:39 GMT
Date: Wed, 11 Oct 2023 08:05:39 GMT
< X-Cache: Error from cloudfront
X-Cache: Error from cloudfront
< Via: 1.1 918e114a1d14f55d896a423c6e63d962.cloudfront.net (CloudFront)
Via: 1.1 918e114a1d14f55d896a423c6e63d962.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: HEL51-P3
X-Amz-Cf-Pop: HEL51-P3
< X-Amz-Cf-Id: mhiDuXDTsi3Ql5WDn19Pp1TU6lTzSEnDs1ya_fvNZD9tOXJI1xUwnQ==
X-Amz-Cf-Id: mhiDuXDTsi3Ql5WDn19Pp1TU6lTzSEnDs1ya_fvNZD9tOXJI1xUwnQ==

<
<!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>504 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection.
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: mhiDuXDTsi3Ql5WDn19Pp1TU6lTzSEnDs1ya_fvNZD9tOXJI1xUwnQ==
</PRE>
<ADDRESS>
</ADDRESS>
</BOD* Connection #0 to host api.soundcloud.com left intact
Y></HTML>

this is a config of my CURL
curl -V

curl 7.81.0 (x86_64-pc-linux-gnu) libcurl/7.81.0 OpenSSL/3.0.2 zlib/1.2.11 brotli/1.0.9 zstd/1.4.8 libidn2/2.3.2 libpsl/0.21.0 (+libidn2/2.3.2) libssh/0.9.6/openssl/zlib nghttp2/1.43.0 librtmp/2.3 OpenLDAP/2.5.16
Release-Date: 2022-01-05
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets zstd

"What am I doing wrong and how can I fix it?"

dpreussler · 2025-10-14T10:53:30Z

dpreussler
Oct 14, 2025
Maintainer

closing as of age, feel free to reopen if needed

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Soundcloud API returns 504 #263

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Soundcloud API returns 504 #263

Uh oh!

Uh oh!

kichkruk Oct 11, 2023

Replies: 1 comment

Uh oh!

dpreussler Oct 14, 2025 Maintainer

kichkruk
Oct 11, 2023

dpreussler
Oct 14, 2025
Maintainer