Expected behavior

To be able to play normally after logging in

Observed/actual behavior

Error message when trying to connect to servers, and after re-logging in with AuthMe.

Steps/models to reproduce

Log in using AuthMe on the server list menu, get the error when trying to connect.

Version

1.18.2

Agreements

• I am running the latest version of the mod.
• My version of Minecraft is supported.
• I have searched for and ensured there isn't already an open issue regarding this.

Other

Error log: https://hastebin.com/tikayologi.yaml

recently getting the same here ... did not change nothing on microsoft minecraft account settings (even tho checked if that might be the cause)
offline player has no issues, just when want to join server as online player this happens

EDIT: fabric 1.18.2 & worked before ... server and client doesn't really say much regarding this except:
server: com.mojang.authlib.GameProfile@c5d878e[id=<null>,name=DadoFlame,properties={},legacy=false] (/[IP]:[PORT]) lost connection: Disconnected (IP & PORT deleted for safety)
client: https://mclo.gs/nHAbM6G#L2393 (link jumps straight to the line when it happens ... but might something stand out in the client logs)

without authme no troubles

I can't seem to reproduce this with my Microsoft account on Minecraft 1.18.2 😕

Hello,

We're getting a similar problem here but on Fabric 1.19.2.

2022-10-28-7.log

This mod actually prevents any connections to the server. Removing it allows the user to log in normally so it's actually hindering access now.

same issue 1.18.2 fabric

Hello,

We're getting a similar problem here but on Fabric 1.19.2.

2022-10-28-7.log

This mod actually prevents any connections to the server. Removing it allows the user to log in normally so it's actually hindering access now.

yep i get the problem too
usually i just wait 2 sec before going in a server and it's fine

Same issue, had to uninstall for now

Same issue here using it for 1.19.2 in a Fabric pack.
If i persist after like 11-12 tries it lets me join in, but it is annoying nonetheless!

Hi, can you please try changing the following settings and see if the issue persists?

methods:
  microsoft:
    authorizeUrl = "https://login.microsoftonline.com/consumers/oauth2/v2.0/authorize"
    tokenUrl = "https://login.microsoftonline.com/consumers/oauth2/v2.0/token"

I'm thinking that perhaps the Microsoft OAuth2 endpoints need updating to these ones.

Hi, can you please try changing the following settings and see if the issue persists?

methods:
  microsoft:
    authorizeUrl = "https://login.microsoftonline.com/consumers/oauth2/v2.0/authorize"
    tokenUrl = "https://login.microsoftonline.com/consumers/oauth2/v2.0/token"

I'm thinking that perhaps the Microsoft OAuth2 endpoints need updating to these ones.

seems to work way better for me, i'll play a few days with that settings to see if i ever encounter the problem again

Let's re-open this issue if the proposed fix does not work.

I am still getting this issue.

I am still getting this issue.

If you had the mod prior to the change you still have the old urls in the config, go reset them

If you had the mod prior to the change you still have the old urls in the config, go reset them

Already have.

I just noticed that waiting five seconds after opening the server list or disconnecting before trying to connect never causes the issue. Also while testing this my session randomly became invalid despite logging in a few minutes ago. This makes me think the problem is actually a rate limit by moj/icrosoft and AuthMe checking the session when the login button is added could be triggering it.

I'm myself also not sure if the mods count depend on it too - as catsoften explained it well, it really seems more of a rate limit as it does mostly happen if clicking join server straight after entering the server list instead of waiting a few seconds

If you had the mod prior to the change you still have the old urls in the config, go reset them

Already have.

I just noticed that waiting five seconds after opening the server list or disconnecting before trying to connect never causes the issue. Also while testing this my session randomly became invalid despite logging in a few minutes ago. This makes me think the problem is actually a rate limit by moj/icrosoft and AuthMe checking the session when the login button is added could be triggering it.

Weird since the update i don't have any issues
But yeah maybe the session checking but that would be extremly weird, your session isn't supposed to be invalid one minute after logging in
I have never encountered a rate limit tho even after spamming the actualize button so i don't really think it could be that actually

Occurring again on Fabric 1.20.1 loader 0.14.22 and 0.14.23

Mod version: 7.0.2+1.20

Can confirm it's happening on Fabric 1.20.1.
Loader version: 0.14.23
Mod version: 7.0.2+1.20

I could try, do you have discord? add me @jadsss

any updates

I did try leave my game open for over 24 hours, and then switching account. I cannot for the life of me reproduce it.

I'm afraid that it's going to have to be up to someone who has the issue on their account to be able to debug it.