-
-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP 403 responses upon trying to do any action #688
Comments
have this issue since ~ 1 month (was facing this issues with Heroic), tried 4 different ISPs in 2 different cities on 3 different distros (archlinux, debian,nobara). i tested a bit, if i run "curl -X GET "https://launcher-public-service-prod06.ol.epicgames.com/launcher/api/public/assets/Windows" |
While I've managed to launch Fortnite as it has a built-in updater in itself, other games have refuse to. I guess Epic has changed something within the API. |
Okay, a little update. I've managed to interact with some stuff by spamming them a bit (5-10 tries). However, you shouldn't attempt this, as I'm brute-forcing it by sending too many requests to the API, which could temporarily ban me. I'm responsible for my own Epic account and IP address. |
This started happening to me just this week too |
Every time I try to interact with anything such as launching a game or getting my apps list, I get some traceback exceptions from the python scripts.
Platform
Operating system and version:
Windows 10 Pro (64-bit)
Legendary version (
legendary -V
):0.20.34
(Windows pre-compiled executable)Expected Behavior
Upon using any commands that interact with the Epic account, the action should be done without any errors.
Current Behavior
Any command throws this error:
Steps to Reproduce
Additional information
The links which appears in the HTTP GET response states something about a missing API endpoint. Everything worked just fine as of yesterday.
I'm also currently unsure whether this is an issue on my end or the Epic's backend, that's why I'm making the issue here.
The text was updated successfully, but these errors were encountered: