mojira.dev

Marc Swenson

Assigned

No issues.

Reported

MCL-5323 Launcher does throw invalid password when VPN enabled Works As Intended

Comments

Johnibur, try /TPing this entity to your position, as I wrote.

Case solved.

Found a workaround.

 

You can get rid of these thingies, when you /tp them to your location:

[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 199a17ca-289b-4991-9746-8a0aa05766b4
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 129de36f-0c73-4ed2-9a65-0b0f051d550a
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 1156de39-eb4b-4e39-a296-92df0a6c7e69
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 9582738d-29d1-427e-a6ee-50a5de9f954b
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 1848fc94-d4f7-4f44-a17b-d79c284ce194
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 43f8091f-49d2-4d5b-b072-ea517f181e34
/kill 199a17ca-289b-4991-9746-8a0aa05766b4
[09:47:30] [Server thread/INFO]: Killed Chicken
/tp 199a17ca-289b-4991-9746-8a0aa05766b4 His_Cifnes
[09:47:40] [Server thread/INFO]: Teleported Chicken to His_Cifnes
/kill 199a17ca-289b-4991-9746-8a0aa05766b4
[09:48:01] [Server thread/INFO]: No entity was found
/tp 129de36f-0c73-4ed2-9a65-0b0f051d550a His_Cifnes
[09:48:28] [Server thread/INFO]: Teleported Chicken to His_Cifnes
/kill 129de36f-0c73-4ed2-9a65-0b0f051d550a
[09:48:33] [Server thread/INFO]: No entity was found
/tp 1156de39-eb4b-4e39-a296-92df0a6c7e69 His_Cifnes
[09:48:46] [Server thread/INFO]: Teleported Chicken to His_Cifnes
/tp 9582738d-29d1-427e-a6ee-50a5de9f954b His_Cifnes
[09:49:02] [Server thread/INFO]: Teleported Chicken to His_Cifnes
/tp 1848fc94-d4f7-4f44-a17b-d79c284ce194 His_Cifnes
[09:49:13] [Server thread/INFO]: Teleported Chicken to His_Cifnes
/tp 43f8091f-49d2-4d5b-b072-ea517f181e34 His_Cifnes
[09:49:21] [Server thread/INFO]: Teleported Chicken to His_Cifnes
/kill 43f8091f-49d2-4d5b-b072-ea517f181e34
[09:49:30] [Server thread/INFO]: No entity was found

No worries.. the chicken never arrived on my locations... so when you have a bugging Zombie, it will not attack you, after /tp. : )

As consequence... the duplicate ID log has never shown up again since /tp. --> works for me..

Confirmed. Got that too, and quite often as well.

Console log produced last time, when somebody was in that chunk:

[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 199a17ca-289b-4991-9746-8a0aa05766b4
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 129de36f-0c73-4ed2-9a65-0b0f051d550a
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 1156de39-eb4b-4e39-a296-92df0a6c7e69
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 9582738d-29d1-427e-a6ee-50a5de9f954b
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 1848fc94-d4f7-4f44-a17b-d79c284ce194
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 43f8091f-49d2-4d5b-b072-ea517f181e34

entered on console, nobody online:

/kill 1848fc94-d4f7-4f44-a17b-d79c284ce194
[Server thread/INFO]: No entity was found

Then I join the server, enter this particular chunk, and the server console says again:

[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 199a17ca-289b-4991-9746-8a0aa05766b4
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 129de36f-0c73-4ed2-9a65-0b0f051d550a
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 1156de39-eb4b-4e39-a296-92df0a6c7e69
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 9582738d-29d1-427e-a6ee-50a5de9f954b
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 1848fc94-d4f7-4f44-a17b-d79c284ce194
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 43f8091f-49d2-4d5b-b072-ea517f181e34

Then, again on the console, I try to kill these entities:

/kill 199a17ca-289b-4991-9746-8a0aa05766b4
[Server thread/INFO]: Killed Chicken
/kill 129de36f-0c73-4ed2-9a65-0b0f051d550a
[Server thread/INFO]: Killed Chicken
/kill 1156de39-eb4b-4e39-a296-92df0a6c7e69
[Server thread/INFO]: Killed Chicken
/kill 9582738d-29d1-427e-a6ee-50a5de9f954b
[Server thread/INFO]: Killed Chicken
/kill 1848fc94-d4f7-4f44-a17b-d79c284ce194
[Server thread/INFO]: Killed Chicken
/kill 43f8091f-49d2-4d5b-b072-ea517f181e34
[Server thread/INFO]: Killed Chicken

It confirmed, the chickens are no longer.

 

But shortly after on the console the EXACT SAME UUIDs appear again, but only because the player is still in that chunk:

[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 199a17ca-289b-4991-9746-8a0aa05766b4
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 129de36f-0c73-4ed2-9a65-0b0f051d550a
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 1156de39-eb4b-4e39-a296-92df0a6c7e69
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 9582738d-29d1-427e-a6ee-50a5de9f954b
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 1848fc94-d4f7-4f44-a17b-d79c284ce194
[Server thread/WARN]: Keeping entity minecraft:chicken that already exists with UUID 43f8091f-49d2-4d5b-b072-ea517f181e34

Wait.. aren't these...?!

 

On the console still, I try if I can kill it again and again and again....

/kill 199a17ca-289b-4991-9746-8a0aa05766b4
[07:53:17] [Server thread/INFO]: Killed Chicken
/kill 199a17ca-289b-4991-9746-8a0aa05766b4
[07:53:26] [Server thread/INFO]: Killed Chicken
/kill 199a17ca-289b-4991-9746-8a0aa05766b4
[07:53:32] [Server thread/INFO]: Killed Chicken

--> Confirmed... it never dies, perhaps it's undead and we need a /heal command to make it die.. :>

Throttled or not. The message is wrong and misleads error tracking.

I am routing through a VPN because I cannot watch Youtube else.
My location is Germany and I am using a german endpoint.. so Germany2Germany.
Disabling the VPN immediately makes stuff work. Or also it helps routing some IPs around the VPN and immediately works too with VPN enabled. But this is st*pid indeed. Why would somebody need to block VPN usage? What do they fear?
Logging into Minecraft via nickname should be enough to authenticate. The location of that user is irrelevant, as usage of VPN was not part of the use policy of Minecraft when I began playing.

I tried several locations, as my VPN provider offers many in some relevant cities all over the world, but none worked with Minecraft.

Mojang support replied "We do not block any IP of that net range", when I sent them some ranges of my VPN provider. Quite weird. It's not blocked but still is?!
Well.. maybe Mojang is not blocking these ranges, but perhaps Amazon does...?! (As MC stuff relies on Amazon cloud services..)

Support has been contacted, but posted me the standard stuff like "reset your password" even though I clearly told them what I already did. For this automated❓ answer I had to wait for five days.

Three days ago I replied with the same words as in this ticket.. no answer yet. This is a major problem, as am I not the only one using that net range, and everybody can't play anymore... furtheron they all are getting the wrong error message.. which misleads support "Password wrong? Just go and reset it.".

Then also blocking a whole provider range just because some users of that range might have mis-behaved (guessing) - What kind of administration is that? If I would work like that at our company, I'd be fired the same month.

If I could atleast get an info which IP the launcher wants to contact, I could build a temporary network route around the VPN, so I could atleast play while my problem is (hopefully) being adressed.

I have contacted support and the bug tracker to get my problem solved. But none of those did. - Why do they exist in the first place, if they cannot do anything?
Furtheron all MC Launcher bugs have been discarded as "invalid" or "works as intended". Looks like the whole category "MCL" can be removed, just to make life easier for the bug tracker team, as all the MCL requests are invalid anyway. .

This appears to be an IP range ban.
Got the same problem, just the other way around:
With VPN enabled: doesn't work
With VPN disabled: does work

Link: https://bugs.mojang.com/browse/MCL-5323

The fact itself (IP banned) is not a bug.. true... but the message itself "password or username wrong" is a bug, since the password and username is absolutely correct. The correct message would be "Your source IP has been banned. Contact support."