-
-
Notifications
You must be signed in to change notification settings - Fork 581
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
Microsoft login failed #1037
Comments
I am able to reproduce |
Happens for me too on Prism 6.3 Trying to use Offline mode also does not work, i guess Offline mode is not that offline haha |
Can any / all of you please send the logs from the file can be found in the Prismlauncher data directory
|
Same issue. Log file```
107.782 D | Opening URL "https://github.com/PrismLauncher/PrismLauncher/issues"
|
This is happening intermittently to me, but hope this information can be useful.
|
I guess it was just something broken on the Microsoft side, its working for some people again. In case you're still not able to play you can try playing Offline (set an invalid proxy on the Settings). |
I can confirm it working again. |
... I bet it would work fine and more reliably if we just had the launcher handle redirects in Auth flows...
EDIT: the 302 is the Qt error code meaning |
you mentioned using wireshark so I'm assuming a level of comfort with network layers I wouldn't normally. If you can replicate this and capture the failed request made to mitmproxy is an ssl capable http proxy, you can set it as the proxy in prism settings and capture the request so long as you follow the steps to import and trust mitmproxy's ca cert. https://docs.mitmproxy.org/stable/concepts-certificates/ even though this is an intermittent problem for people I'm reluctant to say for 100% certain that it's a Microsoft problem. it's grown too frequent. I think there may be a proxy layer in place on microsoft's side that sometimes doesn't like our request. |
Got this as well as of today... |
I had this issue yesterday as well, so it seems to be an ongoing issue – with Microsoft's auth services, presumably. However, I was able to log in today. DRM is pain. |
This comment was marked as off-topic.
This comment was marked as off-topic.
There is literally no difference in the log in code between MultiMC, PolyMC and PrismLauncher. please don't spread FUD |
I never once said there was any difference between the code. I said I was able to login with the other clients just fine if you took two minutes to test that you would know its true. Instead you just yell FUD FUD FUD |
I have been trying to get this to happen again, but it hasn't happened since. |
I got it to work by using the MiniGW version on Windows |
I switched from the MSVC version to the MiniGW version and the issue is persisting. |
please switch back to the msvc version but ensure that you have removed all dlls form prism previous install before installing. If you installed with an installer please run the uninstaller first. if your on a portable install please ensure you remove the tls folder |
There is a similar issue on MultiMC, which suggests that it may be related to the system entering sleep mode. I am not entirely sure that this is the case because my OS has not entered sleep mode in between starting/stopping the launcher. It is also worth mentioning that the issue persists even when the process is ended and restarted. |
Pretty sure it has nothing to do with sleep since it also happens on my Linux desktop which I haven't configured to be able to sleep. |
Update: The issue persists through reboots. The authentication gets stuck on "Working..." regardless of if the account has been added previously, and the Add Microsoft Account also gets stuck on "Working..." I have a working installation on a separate machine. |
Same
Same issue |
I can reproduce this issue on MacOS 13.4 M1 |
I can reproduce this issue. |
As you can see, I've tried a few times
EDIT: Upgraded launcher to 7.1.x, fixed the problem. |
|
Has happened to me on Windows with 8.0 too. |
Duplicate of: #2302 |
Operating System
Windows
Version of Prism Launcher
Prism Launcher 6.3
Version of Qt
Qt 6.4.2
Description of bug
Microsoft account stopped working and trying to log in returns Bad Request according to the launcher.
The whole process works fine and after allowing the account to be linked it gives this error:
Steps to reproduce
Suspected cause
I have no clue what is causing this. Microsoft says everything ran successfully and the response from the Microsoft page is always OK. Prism Launcher interprets something as error 400 but I can't seem to find which request that was because none I can see in Wireshark returned 400
This issue is unique
The text was updated successfully, but these errors were encountered: