Could not log in

[rio_totoda]

Hello... Im a newbie in this game...

I have a problem with the patch client..
When i try too logged in it said "Could not locate server"
I click i again then it said "sh.seatribe.se"
At Homepage, the server is up and 249(more or less) is up...

Will somebody help me???? Thank you...

[Dimsml]

I have a similar problem. When i try to log in, i see the interface and the "loading" sign, but then the game crashes.
I can see an error window but it`s too big and i see only a part of it and i can`t scroll it.

It says:

java.lang.RuntimeException: Delayed error in resource paginae/craft/boiledegg (v2), from forking source backed by HTTP res source (https://www.havenandhearth.com/res/)
at haven.Resource.checkerr(Resource.java:1048)
at haven.Resource.layer(Resource.java:931)
at haven.MenuGrid.cons(MenuGrid.java:74)
at haven.MenuGrid.<init>(MenuGrid.java:96)
at haven.MenuGrid$1.create(MenuGrid.java:48)
at haven.UI.newwidget(UI.java:164)
at haven.RemoteUI.run(RemoteUI.java:58)
at haven.MainFrame.run(MainFrame.java:151)
at haven.MainFrame.main2(MainFrame.java:221)
at haven.MainFrame.access$100(MainFrame.java:34)
at haven.MainFrame$5.run(MainFrame.java:257)
at java.lang.Thread.run(Unknown Source)
Caused by: haven.Resource$LoadException: Load error in resource paginae/craft/boiledegg(v2), from forking source backed by HTTP res source (https://www.havenandhearth.com/res/)
at haven.Resource$Loader.handle(Resource.java:401)
at haven.Resource$Loader.run(Resource.java:375)
... 1 more
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(Unknown Source)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
at haven.Resource$HttpSource.get(Resource.java:330)
at haven.Resource$TeeSource.get(Resource.java:225)
at haven.Resource$Loader.handle(Resource.java:395)
... 2 more
Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed
at sun.security.validator.PKIXValidator.doValidate(Unknown Source)
at sun.security.validator.PKIXValidator.doValidate(Unknown Source)
at sun.security.validator.PKIXValidator.engineValidate(Unknown Source)
at sun.security.validator.Validator.validate(Unknown Source)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(Unknown Source)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
... 17 more

and so on, it`s so long it wont fit into the screen anyway. What should i do ?

[Cookie]

Make sure that your computer's clock is accurate. It says the time stamp failed. If you are set to a different date than the current one it may fail to work.

[Dimsml]

Thx cookie, that helped. Appears that my BIOS battery is dead so the internal clock is wrong.