Failed to login: Invalid session

I added two textfiles. Maybe they can help.
As far as i understand what i read there is that my account is still somehow occupied by someone which makes no sense to me.

Hmm...

[19:20:34 INFO]: Logging in with access token
[19:20:34 ERROR]: Exception whilst logging into profile
com.mojang.authlib.exceptions.InvalidCredentialsException: Invalid token.
	at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:63) ~[launcher.jar:1.6.89-j]
	at com.mojang.authlib.yggdrasil.YggdrasilUserAuthentication.logInWithToken(YggdrasilUserAuthentication.java:132) ~[launcher.jar:1.6.89-j]
	at com.mojang.authlib.yggdrasil.YggdrasilUserAuthentication.logIn(YggdrasilUserAuthentication.java:55) ~[launcher.jar:1.6.89-j]
	at net.minecraft.launcher.Launcher.ensureLoggedIn(Launcher.java:259) [launcher.jar:1.6.89-j]
	at net.minecraft.launcher.Launcher$2.run(Launcher.java:213) [launcher.jar:1.6.89-j]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_131]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
[19:20:36 INFO]: Logging in with access token
[19:20:51 INFO]: Logging in with username & password

[19:21:14] [Realms Notification Availability checker #1/INFO]: Could not authorize you against Realms server: Invalid session id

So, quick update from me.
After 24 hours from my last login on that server, i think some kind of reset kicked in and i was able to play again May 24th. However today May 25th i get exactly the same error as the two days before. The question is, why does that keep happening? I am pretty sure that i will be able to play again tomorrow, but the after i am probably not. I just don't understand what is wrong to cause this kind of error again and again.
If someone experienced this in the past and found a fix for this, i'd be super thankful if you could help me.
_{Mod edit: March -> May}

Bump.
Still need help, please.

So the 24 hour mark from my last logout on my server passed and i am still not able to join any server again. So that what i wrote earlier might be wrong.

I also get the Invalid session issue. my logs are a different, but i also do see "Could not authorize you against Realms server: Invalid session id" in them

What I don't understand is, I'm able to get pass the launcher with my credentials. But when i join server, i get the invalid session issue

Same here. Unable to play since wednesday.

HI, it might be public IP related?
My friend was able to reproduce the below

His Public IP: 41.xxx.xxx.xxx
Login success
Restart Router

Public IP 102.xxx.xxx.xxx
Login Failure
Restart Router

Public IP: 197.xxx.xxx.xxx
Login success
Restart Router

Public IP: 102.xxx.xxx.xxx
Login failure
Restart Router

Public IP: 41.xxx.xxx.xxx
Login success
Restart Router

Seems like the 102 range doesn't work

So with every IP adress that doesn't start with 102, your were able to connect on servers without getting the invalid token error?
Also, it would be interesting to know If you only use ipv4 or ipv6 aswell. Could your friend repeat this test using ipv6?

Hi,

I was also able to reproduce what my friend did. The public IP does indeed seems to be the issue.

I'm currently on the 102.xxx.xxx.xxx range and I was having login issues.

I turned on a tether on my cellphone used that to connect. I checked my public IP on my phones tether and it was the 41.xxx.xxx.xxx range. I could then login in successfully. I could also join my local vanilla server without issue. I closed the launcher and reopened it, and the launcher remembered my credentials and auto logged me in.

I then turn off my tether, reconnect to my wifi. My public IP changes back to the 102.xxx range. All the problems from before appeared again. The launcher failed to auto sign me in, and when I try to join my local server I get the "Failed to Login" issue again.

Obviously the use of mobile data tether is completely unsustainable to play this game as mobile data is ridiculously expensive in my country.

I hope this helps in your solving of the issue

I've uploaded the client and server logs of when I turned on my mobile tether, and then switched back to wifi.

You'll be able to see the success from the tether. And then the failures of when I switched back to my wifi

Im dealing with the same issue, but my public ip is from 185.xxx.xxx.xxx range. And when i change my network to mobile hotspot (with public ip 188.xxx.xxx.xx) i can log in to my multiplayer server without any problems, and launcher remembers my login and password.

I just tried usb thering with my smartphone using mobile data. That seems to work for me aswell. So maybe it's really just our networks which cause the error.

I still have the issue and I'm on the 185.xxx.xxx.xx range as well. I always had the same ip and could play without problems. Since wednesday I couldn't join a server. Since I live close to the border and my mobile doesn't work around here I can't test it via hotspot but I suppose the result would be the same as with you guys. I'm not a pro considering technic and network knowlodge so I'm pretty much out of ideas about what to do. I'd really like to play...

My public IP has been 160.226.249.XXX for the last 11 months and this auth/session issue has only started happening a few days ago for me. So....???

@Liam Owen Wolfe
It's the same with me. My ip didnt change for ages and I was able to play until 23rd of may....

Apperently Mojang is blocking specfic ip ranges. For me 132.xxx.xxx.xxx and 134.xxx.xxx.xxx do not work at all. I am lucky to have two providers and could simply swap to the other one which provides me with an iprange 62.xxx.xxx.xxx which works fine for me.
So the problem actually can't be fixed by us since mojang is causing it. The big question now is, why does mojang block those ip ranges.

Hi Mojang, Is this issue being investigated? Please can you provide an update.

wow... me, too... thanks for the IPs... @mojang: what the hell?

I'll be able to work around this issue but 99,9% of affected people won't

Hello
My ip 185.xxx.xxx.xxx got problems for 4 days. I can join any other servers but One from my friend i cant (I have been playing on this server for a months)
How to fix it?
Pls answer

@unknown, @unknown, @unknown: Did any of you notice that is is weekend ? No one is working at Mojang at this time.
And please stop spamming useless comments. This site is a bugtracker, not customer support.

I'm having the same issue too and what is an ip?

@Kumasasa:

a) one does not block potentially ~80 MILLION customers (if above ranges are really all /8) from using what they paid for without getting some disgruntled ones

b) customer support @ mojang is a joke as is public communication about such issues...

c) this ticket is the ONLY valuable resource about this issue right now - the ONLY one

d) mojang is owned by microsoft. with a corporation like this and a user base like this it is reasonable to expect 24/7 support and people fixing issues that affect lots of people

e) this IS a bug - not in the MC code, ok, but in the critical infrastructure needed to use it fully

I'm sorry but presenting an attitude like you do is exactly the reason why people think lowly of tech support, IT workers and IT in general. Now please stop whining and triage this ticket to someone who might know about why these IP ranges are blocked from authenticating or is even able to fix this. I hope this move isn't justified with some "hardening", "protection" or other excuses because it'd be BS.

a) It is/was a bug. I can guarantee you that Mojang didn't want to block customers.

b) Is it? I just used it last week and they replied real quick.

c) But what's wrong with that? Also, the Mojang status twitter account exists.

d) Just because Mojang is now (since 4 years) owned by Microsoft doesn't mean they got hundereds of employees now. Mojang is not a huge company.

e) Yes. Nobody said it isn't.

The issue should be resolved now, please check whether it actually is.

All further off-topic comments will be removed. Please only comment if you can provide new information about this issue.

I actually have to agree on some points Dominik mentioned. I can understand that the developers don't work on weekend, but this bug came up on wednesday and they could've atleast give some kind of explanation to it, since it was super frustrating looking up this issue. But what pisses me of the most is the error we get. Only a small percentage of the players have some network knowledge and the error we get is completely useless and actually wrong. So how is the majority of the players going to fix this, if the error doesn't provide an actual solution and Mojang keeps saying "we don't know what causes the error".
It took us 4 days to find some kind of solution and now Mojang twitters that they are investigating this. And who knows how long it will take for them to fix that. That's simply not what you'd expect from a big company owned by microsoft.
After this little rent the only thing i'd like to say before i will leave this thread is thank you @Faraaz Sulaiman since you were the one coming up with a first solution for this.

@Bob, I'm happy I was able to help with the investigation. I also do agree with Dominik's post.

@Violine

"The issue should be resolved now, please check whether it actually is."

• I'll test when I get home from work. Thanks.

Also getting the Invalid Session issue on the range 103.xxx.xxx.xxx.

As of the twitter post 1 hour ago saying it's fixed, I'm still getting the issue.