All Actions Fail 403

[b0t]

Im down to go with monthly sub, asked Martin about that like 5-6 years ago …

[kolyamber]

Monthly Sub could be win/win for all, but i assume Martin will need to develop a new SCM for this.

btw i'm also got a 403 with my proxies =\

[Just A User]

Guys this thread is about 403 error's and massive IP bans cloudfront did since friday
This is not about a montly subscription. Martin already said he don't want this.
Simply message Martin to his email account and ask for payment details and send
him some $$ This is how I do it, even if he didn't ask for or want this at all

There's no question he deserves it, he's an excellent programmer and has been
provides us for years the best support we can dream of.

I have SCM working again, Home IP / or expensive residential proxies

[b0t]

Guys this thread is about 403 error's and massive IP bans cloudfront did since friday
This is not about a montly subscription. Martin already said he don't want this.
Simply message Martin to his email account and ask for payment details and send
him some $$ This is how I do it, even if he didn't ask for or want this at all

There's no question he deserves it, he's an excellent programmer and has been
provides us for years the best support we can dream of.

I have SCM working again, Home IP / or expensive residential proxies

Wich version you are using now ?

With 3.729 i cant setup it @ my VPS, even with proxies tested with Chrome at same machine, Soundcloud workin' fine there, but not with SCM.

I have such error here :

****************
Starting: 03.07.2023 15:38
Starting increase plays: https://soundcloud.com/xxx/xxx num: 1111 with: 1 proxies with threads: 1
Scraping track details :https://soundcloud.com/xxx/xxx
403
https://soundcloud.com/xxx/xxx
finished processThread: DbActionStream 1ddbfff3-3adb-46e5-aae2-ef007d36cc39
403
https://soundcloud.com/xxx/xxx proxy: No Proxy Couldn't extract appver from src:

[temp2020]

Expensive residential proxies working on my SCM only with "Play tracks with accounts" Tab.
"Play increaser" show this " Track does not appear to be playable! "

[sleepyboi]

Expensive residential proxies working on my SCM only with "Play tracks with accounts" Tab.
"Play increaser" show this " Track does not appear to be playable! "

Yeah when I add a track to the mass commenter it says invalid track URL so something is definitely happening with it.

Also, Martin I too vote for the monthly subscription to make your work as a developer easier. I've had this software for years now and received more value than the one time payment.

90% of your customers want to pay you every month so please consider it.

[slikoe]

Guys, a monthly subscription fee will not solve the problem, Cloudflare just blocked a wider rang of IP addresses.
It's funny that Soundcloud are shooting themselves at the foot, because many regular people can not access SC at the moment.

[b0t]

Practically for this I bought and tested the proper residental proxies, which work fine in the browser ( about 300$ monthly ),

At the moment the only problem is to run SCM along with the proxy, as I believe. So that all requests go through the proxies.

I may be wrong but it's the only right way to run SCM now on a VPS and not on a local machine.

Let me know if im wrong. Thanks.

P.S. At this point, I am extremely close to starting to use other software for my Soundcloud needs.

Another issue is that I and many other users are willing to pay a monthly subscription for this software and that would be the best motivation for Martin to properly support the project. I don't know if that's the case or not. Just as a thought.

[martin@rootjazz]

Expensive residential proxies working on my SCM only with "Play tracks with accounts" Tab.
"Play increaser" show this " Track does not appear to be playable! "

https://soundcloudmanager.com/updatetesting.html

Any messages saying track not playable are because the input was validated using the machine IP to pull the page, and check it was a valid soundcloud page.

If that request fails because the base IP is blocked from soundcloud or hitting a 403, then it was reporting this.

https://soundcloudmanager.com/updatetesting.html

All those checks removed for the latest version:
https://soundcloudmanager.com/updatetesting.html

So if the proxy can pull soundcloud.com, it should work, but massive ranges of IPs were blocked (although I have been told soundcloud have rolled back the change)

[martin@rootjazz]

Starting: 03.07.2023 15:38
Starting increase plays: https://soundcloud.com/xxx/xxx num: 1111 with: 1 proxies with threads: 1
Scraping track details :https://soundcloud.com/xxx/xxx
403
https://soundcloud.com/xxx/xxx
finished processThread: DbActionStream 1ddbfff3-3adb-46e5-aae2-ef007d36cc39
403
https://soundcloud.com/xxx/xxx proxy: No Proxy Couldn't extract appver from src:

The proxy couldn't view the page, it was blocked. It's as simple as that. Cloudfront are not letting the request hit soundcloud server. There is nothing I can do for this issue. not for $100 not for a $10000000.

Soundcloud added cloudfront protection to their servers. Any HTTP request goes:

machine > cloudfront > soundcloud server

cloudfront are stopping it and returning a 403 instead of relying the request on.