Hello Everyone, Mineraft.net problem

kaosjr · September 5, 2012

Hello, Today I tryed logging into Minecraft using both Minecraft.exe and the Technic Launcher.

I encountered a problem. When i tryed to log into both, they got stuck on the "Connecting to Minecraft.net" bar. They both closed almost instantly when i pressed the "X" button in the corner. (Well, instantly for the Technic Launcher, 10 seconds for the normal Minecraft.exe)

I was wondering if anyone else was having the smae problem this morning.

littleweseth · September 5, 2012

http://questions.technicpack.net/1969/launcher-fails-with-error-cant-authenticate-with-minecraft

Valkon · September 5, 2012

Why were you trying to run both? The Technic Launcher serves the default Minecraft launcher's purpose.

Edit: Hm. Misread this as you trying to use both at the same time.

Anyways, if you can't login to Minecraft.net via the default Minecraft launcher, then it's a problem on Mojang's end.

littleweseth · September 5, 2012

Why were you trying to run both? The Technic Launcher serves the default Minecraft launcher's purpose.

Probably for troubleshooting - if the Technic Launcher doesn't work with a "minecraft.net" error, it's sensible to try the vanilla client to see if it has the same issue.

Valkon · September 5, 2012

Probably for troubleshooting - if the Technic Launcher doesn't work with a "minecraft.net" error, it's sensible to try the vanilla client to see if it has the same issue.

I realized that, though initially I misread it as him trying to run both at the same time.

littleweseth · September 5, 2012

For what it's worth, session.minecraft.net appears to be down:


ping user@helios:~$ ping session.minecraft.net

PING session-1527528893.us-east-1.elb.amazonaws.com (184.73.223.40) 56(84) bytes                                                                                                              of data.

^C

--- session-1527528893.us-east-1.elb.amazonaws.com ping statistics ---

17 packets transmitted, 0 received, 100% packet loss, time 16008ms



 

100% packet loss when pinged.

 

Traceroute doesn't look like much good either:


user@helios:~$ traceroute session.minecraft.net

traceroute to session.minecraft.net (184.73.223.40), 30 hops max, 60 byte packets

<first 10 hops snipped for privacy>

11  203.50.13.134 (203.50.13.134)  91.081 ms  84.315 ms  85.705 ms

12  i-0-5-4-0.sydo-core02.bi.telstraglobal.net (202.84.220.189)  87.908 ms  95.016 ms  95.912 ms

13  i-0-2-0-0.1wlt-core01.bx.telstraglobal.net (202.84.140.21)  235.632 ms  236.545 ms  238.047 ms

14  i-3-4.eqla01.bi.telstraglobal.net (202.84.251.154)  283.254 ms  284.109 ms  286.707 ms

15  63-235-40-45.dia.static.qwest.net (63.235.40.45)  285.136 ms  286.632 ms  287.484 ms

16  * * *

17  72.165.86.90 (72.165.86.90)  344.314 ms 67.133.224.194 (67.133.224.194)  330.286 ms 72.165.86.90 (72.165.86.90)  349.896 ms

18  72.21.220.133 (72.21.220.133)  348.935 ms 72.21.220.165 (72.21.220.165)  332.095 ms  334.223 ms

19  205.251.245.41 (205.251.245.41)  348.763 ms 205.251.245.63 (205.251.245.63)  340.033 ms 72.21.222.157 (72.21.222.157)  346.419 ms

20  216.182.224.17 (216.182.224.17)  342.942 ms 216.182.224.65 (216.182.224.65)  358.308 ms 216.182.224.23 (216.182.224.23)  349.517 ms

21  * * *

22  * * *

23  * * *

24  * * *

25  * * *

26  * * *

27  * * *

28  * * *

29  * * *

30  * * *