Hello everyone. I've got this error since I downloaded the app. It is the first time I use it and my web SoundCloud still works. Can someone help me please?
@Akimixu what operating system are you using? if linux we are having some issues with the new version but the next version (pre-release) is fixed.
Now it may be that we reached the Soundcloud API rate limit. you can open the devtools and check on console what message you get to make sure.
It's been doing this to me too for a couple weeks now. I have no idea what the problem is because it worked fine until one day it randomly just decided not to play :/ I try it every now and then and one time it played one song and then stopped working on the second so that makes it even more confusing.
I'm on Windows 10 64-bit and I'm pretty sure the only thing I changed on my computer the day it stopped was install Titanfall 2 but I can't imagine that had any impact on it.
I went to the twitter page and saw that the new build is on dropbox so I downloaded it and it's stuck on the "Authenticating" screen with two white popups. One says "This popup should automatically close in a few seconds" and the other is blank.
@berickson21 yeah that's the last thing I need to fix before releasing the next version.. that will work only for those logged in before. sorry.
@weblancaster No worries! Thanks for all the work you're putting in! Does that mean that in the meantime if I sign in with the old app the new app will work?
@berickson21 yes the current version on the website is working fine.. but we still have rate limit imposed by Soundcloud API
This is observed on my mac as well.
I am getting this right now too
Console logs: the server responded with a status of 429 (Too Many Requests)
It's working again. Thanks!
Yup, It is working! Thanks for your efforts!
We have a limit of 15 plays daily so when you see status of 429 (Too Many Requests) that's because we reached the limit and Soundcloud block the streaming to Soundnode.
status of 429 (Too Many Requests)
Any workarounds to fix this issue would be appreciated. Thanks!
Wouldn't this be bypassed if every user could manually input their own Client ID/API key?
Go here and look at @wb9688 comment #802
He made a version of soundnode that does the fix automatically. Give it a try. Just look through the comments in that thread until you see him and his fix
If there is a need for that I can make it easy to any user enter it's own token.
When I finish migrating the core to the new framework that can be the next thing I can work.
I think that's a good idea if you can do that. But finish migrating the core first