Linux: "Connection failed : Network error." when connecting to Minecraft.net

[saviola777]

Hi there,

First of all, thanks for this great piece of software, I'm using Minecraft with the FTB-Launcher, and it takes about 10 minutes to start up… Totally annoying when just wanting to reconnect the Minecraft-IRC-Bot which timed out again, this software might just safe me a lot of time! However…

I just pulled the latest version of the client from microzoom.fr/minecraftclient-latest, and I'm using Mono 2.10.9-r2 (because that's the most recent stable version my distribution's package manager is providing). I get the following error(s) upon connecting:

$ mono --trace=E:all MinecraftClient.exe
Console Client for MC 1.4.6 to 1.8.0 - v1.8.0 - By ORelio & Contributors
Username : […]
Password : <******>                                                                                             
Connecting to Minecraft.net...
[0x7febb0952700:] EXCEPTION handling: System.UnauthorizedAccessException: Access to the path "/usr/share/.mono" 
is denied.

"Threadpool worker" tid=0x0x7febb0952700 this=0x0x7febb0c2ec30 thread handle 0x411 state : not waiting owns ()
  at System.IO.Directory.CreateDirectoriesInternal (string) <0x0012f>
  at System.IO.Directory.CreateDirectory (string) <0x00077>
  at System.IO.DirectoryInfo.Create () <0x00013>
  at (wrapper remoting-invoke-with-check) System.IO.DirectoryInfo.Create () <0xffffffff>
  at System.IO.Directory.CreateDirectoriesInternal (string) <0x000df>
  at System.IO.Directory.CreateDirectory (string) <0x00077>
  at System.IO.DirectoryInfo.Create () <0x00013>
  at (wrapper remoting-invoke-with-check) System.IO.DirectoryInfo.Create () <0xffffffff>
  at System.IO.Directory.CreateDirectoriesInternal (string) <0x000df>
  at System.IO.Directory.CreateDirectory (string) <0x00077>
  at Mono.Security.X509.X509Store.CheckStore (string,bool) <0x00037>
  at Mono.Security.X509.X509Store.BuildCertificatesCollection (string) <0x00073>
  at Mono.Security.X509.X509Store.get_Certificates () <0x0001f>
  at Mono.Security.X509.X509StoreManager.get_TrustedRootCertificates () <0x00073>
  at Mono.Security.X509.X509Chain.get_TrustAnchors () <0x00037>
  at Mono.Security.X509.X509Chain.IsTrusted (Mono.Security.X509.X509Certificate) <0x00013>
  at Mono.Security.X509.X509Chain.IsParent (Mono.Security.X509.X509Certificate,Mono.Security.X509.X509Certificat
e) <0x00077>
 at Mono.Security.X509.X509Chain.Build (Mono.Security.X509.X509Certificate) <0x000fb>
  at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.validateCertificates (Mono.Security.X509.X
509CertificateCollection) <0x0039f>
  at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.ProcessAsTls1 () <0x000cf>
  at Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () <0x00056>
  at (wrapper remoting-invoke-with-check) Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () <0xff
ffffff>
  at Mono.Security.Protocol.Tls.ClientRecordProtocol.ProcessHandshakeMessage (Mono.Security.Protocol.Tls.TlsStre
am) <0x0009f>
  at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (System.IAsyncResult) <0x0028c>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object (object,intptr,intptr,intptr) <0xfffff
fff>
[0x7febb0952700:] EXCEPTION handling: System.Security.Cryptography.CryptographicException: Unsupported hash algo
rithm: 1.2.840.113549.1.1.11

"Threadpool worker" tid=0x0x7febb0952700 this=0x0x7febb0c2ec30 thread handle 0x411 state : not waiting owns ()
  at Mono.Security.X509.X509Certificate.VerifySignature (System.Security.Cryptography.RSA) <0x001e7>
  at Mono.Security.X509.X509Chain.IsParent (Mono.Security.X509.X509Certificate,Mono.Security.X509.X509Certificat
e) <0x00113>
  at Mono.Security.X509.X509Chain.Build (Mono.Security.X509.X509Certificate) <0x000fb>
  at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.validateCertificates (Mono.Security.X509.X
509CertificateCollection) <0x0039f>
  at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.ProcessAsTls1 () <0x000cf>
  at Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () <0x00056>
at (wrapper remoting-invoke-with-check) Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () <0xff
ffffff>
  at Mono.Security.Protocol.Tls.ClientRecordProtocol.ProcessHandshakeMessage (Mono.Security.Protocol.Tls.TlsStre
am) <0x0009f>
  at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (System.IAsyncResult) <0x0028c>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object (object,intptr,intptr,intptr) <0xfffff
fff>
[0x7febb0952700:] EXCEPTION handling: Mono.Security.Protocol.Tls.TlsException: Invalid certificate received from
 server.

"Threadpool worker" tid=0x0x7febb0952700 this=0x0x7febb0c2ec30 thread handle 0x411 state : not waiting owns ()
  at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.validateCertificates (Mono.Security.X509.X
509CertificateCollection) <0x0075b>
  at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.ProcessAsTls1 () <0x000cf>
  at Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () <0x00056>
  at (wrapper remoting-invoke-with-check) Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () <0xff
ffffff>
  at Mono.Security.Protocol.Tls.ClientRecordProtocol.ProcessHandshakeMessage (Mono.Security.Protocol.Tls.TlsStre
am) <0x0009f>
  at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (System.IAsyncResult) <0x0028c>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object (object,intptr,intptr,intptr) <0xfffff
fff>
[0x7febb0b53700:] EXCEPTION handling: Mono.Security.Protocol.Tls.TlsException: Invalid certificate received from
 server.
"Threadpool worker" tid=0x0x7febb0b53700 this=0x0x7febb0c2eea0 thread handle 0x40f state : not waiting owns ()
  at Mono.Security.Protocol.Tls.RecordProtocol.EndReceiveRecord (System.IAsyncResult) <0x00103>
  at Mono.Security.Protocol.Tls.RecordProtocol.ReceiveRecord (System.IO.Stream) <0x00027>
  at Mono.Security.Protocol.Tls.SslClientStream.SafeReceiveRecord (System.IO.Stream) <0x00027>
  at Mono.Security.Protocol.Tls.SslClientStream.OnNegotiateHandshakeCallback (System.IAsyncResult) <0x00043>
  at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (System.IAsyncResult) <0x0008d>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object (object,intptr,intptr,intptr) <0xfffff
fff>
[0x7febb0b53700:] EXCEPTION handling: System.IO.IOException: The authentication or decryption has failed.

"Threadpool worker" tid=0x0x7febb0b53700 this=0x0x7febb0c2eea0 thread handle 0x40f state : not waiting owns ()
  at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (System.IAsyncResult) <0x00133>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object (object,intptr,intptr,intptr) <0xfffff
fff>
[0x7febb3afd740:] EXCEPTION handling: System.IO.IOException: The authentication or decryption has failed.

"<unnamed thread>" tid=0x0x7febb3afd740 this=0x0x7febb3957ea0 thread handle 0x403 state : not waiting owns ()
  at Mono.Security.Protocol.Tls.SslStreamBase.EndRead (System.IAsyncResult) <0x0014b>
  at System.Net.Security.SslStream.EndAuthenticateAsClient (System.IAsyncResult) <0x0003e>
  at System.Net.Security.SslStream.AuthenticateAsClient (string,System.Security.Cryptography.X509Certificates.X5
09CertificateCollection,System.Security.Authentication.SslProtocols,bool) <0x00052>
  at System.Net.Security.SslStream.AuthenticateAsClient (string) <0x00037>
  at MinecraftClient.Protocol.ProtocolHandler.doHTTPSPost (string,string,string,string&) <0x00087>
  at MinecraftClient.Protocol.ProtocolHandler.GetLogin (string&,string,string&,string&) <0x00123>
  at MinecraftClient.Program.InitializeClient () <0x000eb>
  at MinecraftClient.Program.Main (string[]) <0x0050f>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <0xffffffff>

I did execute mozroots --import --ask-remove, as suggested in the minecraftforum thread on MCC, beforehand. Is this a known error? Is this related to the Mono version? If so, you might want to consider adding a minimum required version somewhere.

Oh and you might want to consider using the colors of the shell for output (or just one color for everything)--I use a grey background color in my shell and it took me a while to figure out that there was actually output--just in the same color as my background, hence invisible. :P

Thanks in advance.

[ORelio]

Hello,

Seems like it's the same issue as described in the forum, and after running the mozroots commands it was solved on my side when testing. The bug is that in the latest version (1.8.0) it incorrectly displays 'Network error' instead of 'SSL error'. This bug is already solved in commit 8eb71bd, which will be included in next version.

If you cannot login even after running the mozroots --import --ask-remove command i'd suggest you either to update the certificates with mozroots --sync --ask-remove or to update mono, because it is a SSL error and thus there is a problem in certificates or certificate handling in your mono installation. Alternatively, if you still cannot run it properly in Mono, you might want to try Wine with .Net framework 4.0.

Regarding colors, I'll try to handle this on startup, but currently the background color should be set to black automatically after logging in in order to print colors correctly. And that's a bit weird because at the beginning, the text color is not explicitely set to grey, so it should have the default font color of your terminal.

[saviola777]

Okay, I updated to Mono 3.0.7, which solves the problem described above. However, I'm now stuck right after that:

Retrieving Server Info...
Server version : MC 1.6.4 (protocol v78).
Version is supported.
Logging in...
Handshake successful. (Server ID: -12055b68627071bd)
Crypto keys & hash generated.
Checking Session...

And that's it. Any ideas? Will try it later on Windows to rule out the possibility that it's somehow related to this specific server.

And you are of course correct regarding the colors: it only switchted to grey after the "Connecting to Minecraft.net" line.

Edit: Okay, doesn't work in Windows either, but it gives me more error messages:

Login failed :
You don't have FML installed, you cannot connect to this server
[…]

Well, I guess I could have assumed that this client is not compatible with Minecraft Forge :[

[ORelio]

Sorry but currently yes, it's not compatible with Forge.
Strange it did not display the login failed message on linux, though.

[saviola777]

No problem, I wasn't aware of how much Forge changes the client, and I have no idea how much work Forge-compatibility would be; it's probably not worth it (right now).

Thanks for the feedback! I'll close the issue then.