Getting 403 on 0.9.3 but not on 0.9.1
Closed this issue · 11 comments
Above is 0.9.3 failing and 0.9.1 running just fine
My configs are practically identical.
configs_0.9.1.zip
configs_0.9.3.zip
It should be "remote" server and not "remove" I assume
This might be something you have to take up with the BeatSaver admins. Since it used to work and now it doesn't, I'm guessing they blocked your IP + BeatSyncConsole's UserAgent (just version 0.9.3). The BeatSyncConsole v0.9.3 release works on my PC.
This was my first time using 0.9.3 and neither of my connections works
I'm seeing the same issue, first time using it (also on Linux, is the user agent different for Linux vs Windows builds?)
Edit: Confirmed, line 291 of Program.cs:
SongFeedReaders.WebUtils.WebClient.SetUserAgent($"BeatSyncConsole/{version} ({RuntimeInformation.OSDescription}){VersionInfo.Description}");
Would it be possible to get a test build setup with the OSDescription set to lie and say I'm on Windows? Or using Firefox? I don't have Visual Studio to try and build this myself. I can download the files with Firefox so it's not an IP ban, it seems something with BeatSyncConsole's user agent is being blocked by BeatSaver.
What Linux distro are you using? It was working when I tested with Ubuntu.
I'm on Arch. Is such a specific user agent really necessary? I'm not sure how to get in touch with BeatSaver to try and get mine whitelisted... the github says it's only for the code and not hosting issues.
Nevermind, it doesn't work in Ubuntu anymore. Not sure what's going on, I thought Beat Saver used a blacklist not a whitelist. Guess I'll go back to the generic, boring User-Agent.
That would be awesome if it worked. I was asking around in the BS mod Discord's #pc-help channel for a few days and didn't get a single reply on the topic of getting unblocked BeatSaver, tried multiple times and just crickets. I somewhat suspect it will need to just be Firefox or Chrome or something at this point as whoever runs it does not seem to be easy to contact (only contact info on the website is for DMCA and the github explicitely says they don't run the website, so no idea where to go for Cloudflare configuration issues).
Actually, I think I might've just published the wrong tar.gz file for Linux in the Releases page. The latest Actions build works.
https://github.com/Zingabopp/BeatSync/actions/runs/879752737
This should be fixed in v0.9.4.
Yes, it's working now, thanks!
0.9.4 does indeed solve the problem, thank you.