Can't comment 'Setup auth src null or empty:' error

[babe]

I have tested with different proxies including brand new dedicated proxies. I also tested by manually log in, search and comment using the same proxies and they are fast.

Saving new cookies: lkwishart
Get user details: https://soundcloud.com/lkwishart: lkwishart
Comment on track: https://soundcloud.com/cody-fritz-57633 ... see-it-all with: lkwishart
Comment on track with user: lkwishart Track: https://soundcloud.com/cody-fritz-57633 ... see-it-all
Play track: https://soundcloud.com/cody-fritz-57633 ... see-it-all
* SUCCESS: account play registered: https://soundcloud.com/cody-fritz-57633 ... see-it-all
Setup auth
* FAILED: Setup auth src null or empty: https://soundcloud.com/connect/token?cl ... e%20upload
* FAILED play track: https://soundcloud.com/cody-fritz-57633 ... see-it-all: 9345857 : Couldn't pull auth URL source
Made: 0 of limit: 9: action: Track Comment: using: lkwishart

Setup auth
* FAILED: Setup auth src null or empty: https://soundcloud.com/connect/token?cl ... e%20upload
9345857 : Couldn't pull auth URL source
Couldn't pull auth URL source

[babe]

Rolling back to an old version solved the problem... this is a bug

[martin@rootjazz]

running tests here

[martin@rootjazz]

Am not seeing any issue here. Are you running many actions with the same proxies? It could be the overuse issue as per your other thread

[martin@rootjazz]

have added some debugging to try and find out more about the issue

[martin@rootjazz]

https://soundcloudmanager.com/updatetesting.html

[babe]

Am not seeing any issue here. Are you running many actions with the same proxies? It could be the overuse issue as per your other thread

I concluded the same reason first and bought some brand new private proxies but still get the same errors. I rolled back to an old version, 3.314 I believed and the errors were all gone.

[martin@rootjazz]

If it is the same issue as the other thread, then rolling back wasn't the fix, just the time it took to do it. Your other area, is clearly logged as "too many requests", which is overuse. Whatever temp block you might have had would have passed whilst reinstalling.

But without logs, these are all assumptions. If you are happy on the old version then

[babe]

I just upgraded to the latest testing version and all problems were gone.

[babe]

It just had the same errors again so I rolled back to 3.314 and everything is back to normal again.