soundcloud.com: Sorry! Something went wrong
If you have any questions about the content on this page, don’t hesitate to open a new ticket and we’ll do our best to assist you.
Sorry! Something went wrong
Scenario: you go to soundcloud.com, and you are greeted with the message:
Sorry! Something went wrong
Is your network connection unstable or browser outdated?
Misleading hint: Is your network connection unstable or browser outdated?
Help centre
Fortunately, or so you think, soundcloud has been nice enough to provide a link to the Help Center. You go there, but then you don’t see any category that seem to cover your current problem. If you are astute enough, you might guess that your problem is somehow related to cookies.
No help category seem to cover our problem at hand.
Back to square one!
If you rightly guessed that your problem was cookie-related, and clicked on the appropriate help menu, you are, again, greeted with the initial error message. Notice the address of the page: in case you have a cookie problem, you cannot get any help about your cookie problem until you solve, on your own, your cookie problem!
Getting help about cookies is no cookie when you don’t have cookies enabled!
Solution
You’ve guessed it: to solve the problem, simply go to your browser settings and enable cookies. Limit the cookies validity to the current session, if you don’t want to be tracked over the long term.
Sorry, something went wrong – SoundCloud
Are you currently experiencing an error message while trying to load SoundCloud.com? Each time you attempt to load a SoundCloud webpage, repost a track, like a track, message another user, or another action you get Sorry, something went wrong.
If you are currently experiencing this error, use the comment form below to share about it and see if others are also experiencing the issue in real-time.
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
soundcloud / api Public
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
LOGIN IS BROKEN (fixed) #212
LOGIN IS BROKEN (fixed) #212
Comments
Cannot login to Soundcloud via soundcloud.com or API connect flow. Error message: «Something unexpected happened. Please try again.» Same for multiple accounts.
Started this morning. Is anyone else experiencing this?
UPDATE: Can now login again at 11:58 AM, Thursday, May 26, 2022 (EDT). What happened?
The text was updated successfully, but these errors were encountered:
Ah, so about 15:30 UTC, all their token endpoints returned 500 internal service error, so we busted our caches while refreshing tokens and now have bounced off rate limits
According to the corresponding email thread, it looks like the issue could be resolved on your side.
Thanks for the reply.
I think the issue is a bit deeper than that here with this particular use case.
As a general request — it would be great if we could get the documented rate limits for various endpoints/actions so we can configure circuit breakers correctly to not overload SoundCloud API and get locked out when an issue does occur. I’m aware of a global rate limit at SoundCloud: #189 and this is what we currently use with our circuit breakers.
However, in this particular case, it appears the rate limit is for /oauth/token , and specifically for the client-credentials-exchange . It was my understanding that we are limited to being granted 50 tokens in 24 hours (https://github.com/soundcloud/api/releases/tag/2021-09-07). This as a rate limit makes sense, and the rate limit is issued to a clientId, not an IP. However, an aggressive edge rate limit of 30 requests in 1 hour for a specific IP means we wouldn’t have been able to protect against hitting this rate limit last night because the limits are far to low to allow for effective circuit breaking
What happened for us yesterday was that we tried to refresh a server token (client-credentials-exchange), and got back a 500. At this point, we have to cache bust our access token and refresh token as we don’t know if the refresh token is valid anymore, and we need to go back to a consistent state. We then retry this token grant process until we can get a token, ignoring these server errors as the token hasn’t actually been granted. As an example, even with retries set to 10s back off, we would still run out of available hourly API requests for this specific endpoint within a few minutes. For us the API was returning 500, which indicates a server side issue, and we should retry. Unfortunately this retry was counted towards our rate limits, and eventually we got locked out for an hour.
Does this new rate limit replace the 50 server side tokens per hour (https://github.com/soundcloud/api/releases/tag/2021-09-07)? Or is in addition to?
Are there any rate limits on other endpoints other than the global one I mentioned earlier? It would be great to find this out so we can correct our circuit breaker settings going forward if they aren’t right.
I would also request that this particular rate limit is lifted to something which we can effectively have a back off or circuit breaker approach with. 10 requests in a minute would be workable for example, but ideally higher than that for cases of failure. Or I guess if server side failures didn’t count towards the consumption client rate limits that could be workable as well?
Sorry something went wrong soundcloud что делать
Reddit and its partners use cookies and similar technologies to provide you with a better experience.
By accepting all cookies, you agree to our use of cookies to deliver and maintain our services and site, improve the quality of Reddit, personalize Reddit content and advertising, and measure the effectiveness of advertising.
By rejecting non-essential cookies, Reddit may still use certain cookies to ensure the proper functionality of our platform.
For more information, please see our Cookie Notice and our Privacy Policy .