Error client wont start

[Thyme]

No idea what is going on with this but it sure is happening
It only does it when I log in
Default client

java.lang.NullPointerException
at com.sun.deploy.security.DeployAuthenticator.getPasswordAuthentication(Unknown Source)
at com.sun.javaws.JAuthenticator.getPasswordAuthentication(Unknown Source)
at java.net.Authenticator.requestPasswordAuthentication(Unknown Source)
at java.net.SocksSocketImpl$2.run(Unknown Source)
at java.net.SocksSocketImpl$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.SocksSocketImpl.authenticate(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at haven.HackSocket.connect(HackSocket.java:105)
at haven.HackSocket.connect(HackSocket.java:112)
at haven.SslHelper.connect(SslHelper.java:155)
at haven.AuthClient.<init>(AuthClient.java:49)
at haven.Bootstrap.run(Bootstrap.java:144)
at haven.MainFrame.run(MainFrame.java:257)
at java.lang.Thread.run(Unknown Source)

[Granger]

Please read and follow the Bug report creation HOWTO

Not giving any information about your machine will not help in solving your issue.

[loftar]

at java.net.SocksSocketImpl.authenticate(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)

From this, it seems your Java installation is set to use a SOCKS proxy for whatever reason. Disabling that will probably fix it.

[Thyme]

at java.net.SocksSocketImpl.authenticate(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)

From this, it seems your Java installation is set to use a SOCKS proxy for whatever reason. Disabling that will probably fix it.

I do use a proxy to access haven sometimes is this not okay?

[loftar]

I do use a proxy to access haven sometimes is this not okay?

I haven't actually examined the situation of using proxies very much at all myself. All I see is that the reason for the exception you're getting is that Java is somehow unable to use the proxy that has been configured for it.

I mean, if anything I think it's strange that Java is throwing NPEs even from having a bad proxy configuration (I would think that it should throw some more explanatory error), so it might even be that there's some bug in Java's SOCKS implementation, but I can't really speak about such details as I don't know how Java's proxy implementation works; all I know is that the error is caused by it. Also, this is clearly a problem with Java's SOCKS proxy implementation in particular. Is that the kind of proxy you're using?

[MagicManICT]

Make sure your proxy information is configured correctly. If there's another means of configuring your proxy connection, you might try that instead. This might show if there's an issue in the configuration or with the implementation (bug in Java). Depending on what you're using for a proxy service (personal computer in another location, rented services, or other), you might need to make sure it's running properly, too.