mojira.dev

Mikhail S.

Assigned

No issues.

Reported

MCL-19488 Microsoft Login doesn't work in MC, but works everywhere else. Invalid

Comments

Still present in 1.19.1.
Right-clicking with lava bucket cause the ore to lit and thats it.

You can still pour lava if you Shift+RMB

Manually putting ip address from public dns for device.auth.xboxlive.com in hosts fixes the problem entirely tho.

 

Like, I see strings like "[Info: 2021-09-05 20:57:49.5789923: NetQueue.cpp(428)] NetQueue: Primary ip: 152.199.21.175, Host: piston-meta.mojang.com" and it Looks like it's getting ip address from somewhere. Why it can't do the same for domains like device.auth.xboxlive.com?

I can see in Launcher Log errors connecting to these:

[Info: 2021-09-05 20:27:07.8934782: NetQueue.cpp(466)] NetQueue: Action failed with result "Failed to connect to device.auth.xboxlive.com port 443: Connection refused" (7) : device.auth.xboxlive.com
[Info: 2021-09-05 20:27:07.8934958: NetQueue.cpp(504)] NetQueue: Action finished: device.auth.xboxlive.com
[Info: 2021-09-05 20:27:07.8935226: NetQueue.cpp(532)] NetQueue: Action finalized: device.auth.xboxlive.com

 

[Error: 2021-09-05 20:27:35.7198982: XalApi.cpp(600)] Failed to sign-in with UI while switching account. XAL Status: 8
[Error: 2021-09-05 20:27:35.7199872: UserIdentity.cpp(170)] Failed to switch account. XAL status: 8
[Info: 2021-09-05 20:27:35.7200276: UnifiedAccounts.cpp(290)] MSA sign-in failed
[Error: 2021-09-05 20:27:37.9226002: NetQueue.cpp(425)] NetQueue: No ip address available. Error code 7, Host: vortex.data.microsoft.com
[Info: 2021-09-05 20:27:37.9226483: NetQueue.cpp(466)] NetQueue: Action failed with result "Failed to connect to vortex.data.microsoft.com port 443: Address not available" (7) : vortex.data.microsoft.com
[Info: 2021-09-05 20:27:37.9226659: NetQueue.cpp(504)] NetQueue: Action finished: vortex.data.microsoft.com
[Info: 2021-09-05 20:27:37.9226926: NetQueue.cpp(532)] NetQueue: Action finalized: vortex.data.microsoft.com
[Info: 2021-09-05 20:27:40.6729549: NetQueue.cpp(585)] NetQueue: Starting net action vortex.data.microsoft.com
[Error: 2021-09-05 20:27:42.8740433: NetQueue.cpp(425)] NetQueue: No ip address available. Error code 7, Host: vortex.data.microsoft.com
[Info: 2021-09-05 20:27:42.8740902: NetQueue.cpp(466)] NetQueue: Action failed with result "Failed to connect to vortex.data.microsoft.com port 443: Address not available" (7) : vortex.data.microsoft.com

 

Both of them being traced to loopback interface cause of hosts file.

You can legit put "*.msads.net" in the search bar and see how many people recommend blocking it.

 

It also sounds like a wheel in a stick by me, but the thing is that I'm not the only person who's having such problem. But is losing a playerbase of privacy-aware people worth it? Not to mention that there are probably kids, who can't control their parents firewall and won't be able to do anything with that.

I don't see changing auth process as a huge problem, especially when you can probably get Microsoft help to do it in a way it's done in MSVS, for example.