Error "Something went wrong. I can't play this track :(" #910

Closed
Akimixu opened this Issue Nov 16, 2016 · 18 comments

Projects

None yet

8 participants

@Akimixu
Akimixu commented Nov 16, 2016 edited

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?

screenshot_1

@weblancaster
Member

@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.

@berickson21

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.

@berickson21

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.

@weblancaster
Member

@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.

@berickson21
berickson21 commented Nov 17, 2016 edited

@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?

@weblancaster
Member

@berickson21 yes the current version on the website is working fine.. but we still have rate limit imposed by Soundcloud API

@sadanand-garikapati

This is observed on my mac as well.

@JMccormick264

I am getting this right now too

@ChristopherNeuwirth

Console logs: the server responded with a status of 429 (Too Many Requests)

@ChristopherNeuwirth

It's working again. Thanks!

@Akimixu
Akimixu commented Nov 28, 2016

Yup, It is working! Thanks for your efforts!

@weblancaster
Member

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.

@g0to
g0to commented Dec 2, 2016

Any workarounds to fix this issue would be appreciated. Thanks!

@Martan404

Wouldn't this be bypassed if every user could manually input their own Client ID/API key?

@JMccormick264
JMccormick264 commented Dec 6, 2016 edited

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

@weblancaster
Member
weblancaster commented Dec 6, 2016 edited

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.

@JMccormick264

I think that's a good idea if you can do that. But finish migrating the core first

@weblancaster weblancaster referenced this issue Dec 12, 2016
Closed

No Sound #922

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment