-
-
Notifications
You must be signed in to change notification settings - Fork 598
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
Prism can't reach to microsoft for account authication, and can't even add an account to it #1904
Comments
Something is blocking PrismLauncher network requests. Try: |
Firewalls isn't blocking prism, I already am using portable version and I am using a fresh portable version, nothing else touch beside account |
I have the same issue. I played perfectly fine 2 days ago, but trying to play today I can't log in. I tried to remove my account and log back in, and after authenticating with Microsoft I get These are the relevant parts of the logs:
The official Minecraft Launcher and the FTB App both work fine. I tried the portable version, the deb and the AppImage, and they're not working either (I normally use the Flatpak). |
Visiting the site throws an "The request is blocked" error, so that may be why it's not connecting. Edit: After posting this comment, I went and tested removing and re-adding an alt account, and it works perfectly. Which is weird because I just said that on the API website mentioned above, it says "The request is blocked" and based on other reports here it shouldn't be working? |
It started working for me again too. I'm not sure what happened initially though, especially considering I only had an issue with Prism Launcher |
Duplicate of: #2302 |
Operating System
Windows
Version of Prism Launcher
Prism Launcher 8.0
Version of Qt
6.6.0
Description of bug
The launcher couldn't reach to auth server and can't reach to Microsoft to log in
PrismLauncher-0.log
PrismLauncher-0 (1).log
Steps to reproduce
Just refresh or try to click add account
Suspected cause
No response
This issue is unique
The text was updated successfully, but these errors were encountered: