gorilla-devs / GDLauncher

GDLauncher is a simple, yet powerful Minecraft custom launcher with a strong focus on the user experience
https://gdevs.io
GNU General Public License v3.0
1.21k stars 261 forks source link

Error occurred while logging into minecraft #1473

Open kcoderhtml opened 1 year ago

kcoderhtml commented 1 year ago

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Login with Microsoft acount
  2. See error

Expected behavior I would be able to log in

Possible solutions Not sure

Screenshots Screenshot_2022-11-07-09-00-11_3520x1080

Operating System:

Additional context N/A

kcoderhtml commented 1 year ago

After installing the minecraft launcher from the aur I was able to successfully login with these errors image

Eskaan commented 1 year ago

1449 might be related.

RileyMills commented 1 year ago

I'm having the same issue. I was able to log in a couple days ago, but now I can't. I'm getting a couple of varied errors in the console:

HTTP 429 from https://api.minecraftservices.com/authentication/login_with_xbox HTTP 400 from https://login.live.com/oauth20_token.srf with response body:

{"error":"invalid_grant","error_description":"The provided value for the 'code' parameter is not valid.","correlation_id":"9908619b-830f-43a2-959f-1c7d9e152d26"}

The only thing different for me lately is that I've enabled the Microsoft Authenticator for my Microsoft account. I did notice the login process for minecraft.net was a little flakey earlier today, so I don't know if this is something new with Microsoft's SSO process.

Operating System:

IgorMael commented 1 year ago

I was receiving the same error 10 minutes ago, now it seems to be fixed. Maybe it returned for you too. Probably was a issue at minecraft servers.

Korilos commented 1 year ago

I have the same problem. minecraft

Operating System:

OS: MacOS 10.13.6
Launcher Version: [v1.1.29]
Java Version: [N/A]
Minecraft Version: [N/A]
Mod Loader: [N/A]
kcoderhtml commented 1 year ago

Also got this error:

20:16:16.884 › Trying to start listener
20:16:16.885 › Started listener
actions.js:145 i
(anonymous) @ actions.js:145
launchermeta.mojang.com/mc/game/version_manifest.json?timestamp=1667870176822:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED
actions.js:228 Object Object Object Object
(anonymous) @ actions.js:228
20:16:17.722 › Unable to initialize Discord RPC: Error: Could not connect
    at Socket.p (/usr/lib/gdlauncher/build/electron.js:1:16446)
    at Object.onceWrapper (node:events:514:26)
    at Socket.emit (node:events:394:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
actions.js:574 i
(anonymous) @ actions.js:574
sessionserver.mojang.com/session/minecraft/profile/c4d107ec2857442aae83eb82423184d2:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED
actions.js:842 i
(anonymous) @ actions.js:842
Login.js:175 Error: AxiosError: Network Error
    at actions.js:843
    at f (regeneratorRuntime.js:86)
    at Generator._invoke (regeneratorRuntime.js:66)
    at Generator.throw (regeneratorRuntime.js:117)
    at r (asyncToGenerator.js:3)
    at c (asyncToGenerator.js:29)
(anonymous) @ Login.js:175
sessionserver.mojang.com/session/minecraft/profile/c4d107ec2857442aae83eb82423184d2:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED
actions.js:786 i
(anonymous) @ actions.js:786
actions.js:842 Error: Error occurred while logging in Minecraft.
    at actions.js:787
    at f (regeneratorRuntime.js:86)
    at Generator._invoke (regeneratorRuntime.js:66)
    at Generator.throw (regeneratorRuntime.js:117)
    at r (asyncToGenerator.js:3)
    at c (asyncToGenerator.js:29)
(anonymous) @ actions.js:842
Login.js:175 Error: Error: Error occurred while logging in Minecraft.
    at actions.js:843
    at f (regeneratorRuntime.js:86)
    at Generator._invoke (regeneratorRuntime.js:66)
    at Generator.throw (regeneratorRuntime.js:117)
    at r (asyncToGenerator.js:3)
    at c (asyncToGenerator.js:29)
(anonymous) @ Login.js:175
api.minecraftservices.com/authentication/login_with_xbox:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED
Eskaan commented 1 year ago

Name not resolved is a DNS issue. That is not our fault, rather your computer not reaching the authentication services. About the above one, 429 is a HTML status code that specifies that you have done too many requests. That is also unrelated to our launcher and a problem with the Microsoft authentication (or you trying to often)

kcoderhtml commented 1 year ago

Thanks for the help I'll look into the DNS issue

Eskaan commented 1 year ago

It is more likely that the servers were down at that time.

kcoderhtml commented 1 year ago

If I paste the link into the browser it works https://sessionserver.mojang.com/session/minecraft/profile/c4d107ec2857442aae83eb82423184d2

RileyMills commented 1 year ago

Quick followup: It seems to have also resolved itself for me. I'm guessing an outage or other issue with the XBL login servers 🤷

ReiDaTecnologia commented 1 year ago

For me the web page aren't even loading... image Weirdly enough, i was logged in... but for some reason GDL decided to logout?

kcoderhtml commented 1 year ago

It works for me now, but I switched back from arch to Pop OS.

Eskaan commented 1 year ago

For me the web page aren't even loading...

That looks more like a Mojang or local internet problem to me. Could you try try reproducing it and look if you're on the latest version (v1.1.29 / v1.1.30-beta.1)?

ReiDaTecnologia commented 1 year ago

I think mojang and microsoft servers went down or something as i can't access minecraft.net, mojang.com and even my email (outlook)...

Sowrish17 commented 1 year ago

I've tried many times log into my Microsoft account but it doesn't let me.So if anyone has a solution to it, please reply to me. 16775035961119036432762437939926

Fuzzypyro commented 1 year ago

Issue has to be DNS related. I saw in the logs a statement that the url could not be resolved. I fixed it via a vpn tunnel to another location that used google dns. I will explore more into the issue after a good gaming session and report back with logs and whatnot.