Follows not working

[shaner4042]

followings stopped working again today for me (repost,like, comment still works). Giving the same error as before again now:

* ERROR: CheckFollowing: The remote server returned an error: (401) Unauthorized.

Using MASS follow tab to follow a user. Fails w/ and without proxy, using multiple accounts.

LOGS: 21000

[martin@rootjazz]

you are an update behind, can you check it

https://soundcloudmanager.com/updatetesting.html

[shaner4042]

you are an update behind, can you check it

https://soundcloudmanager.com/updatetesting.html

I am running the latest testing update.

Follows are working very sporadically (only about 1 in 20 accounts perform a successful follow action) despite 100% success with all my accounts a few days ago. Accounts haven't been overworked, and are well below the daily limits for any action. Tried w/ and without proxies. Other actions such as like and repost work with the same accounts. Manual follows with accounts through the browser work, but through SCM it fails. Given this error:

* ERROR: CheckFollowing: The remote server returned an error: (401) Unauthorized.

LOGS: 39214

[martin@rootjazz]

you are an update behind, can you check it

https://soundcloudmanager.com/updatetesting.html

I am running the latest testing update.

ok I see the latest logs are the latest update. Seems to be a problem with checking the followingsIds endpoint. Let me run some tests here

[martin@rootjazz]

ok I've found the issue, as you say, doesn't happen all the time and will be effected by what the account has done previous this session to affect the headers / cookies


Update should be ready within the hour



Regards,
Martin

[martin@rootjazz]

https://soundcloudmanager.com/updatetesting.html

Let me know if the issue persists



Regards,
Martin

[randomguy]

Dear martin,
followers still not working on latest update.

[martin@rootjazz]

Dear martin,
followers still not working on latest update.

logs please (always submit logs as can save time as 9/10 they are always needed and we don't need another round of back and forth communication)

[randomguy]

logs_69504 submitted please check.

[martin@rootjazz]

strange, your logs indicate the update wasn't firing, but there was a build issue. Let me test and get a new one for you


Regards,
Martin