Page MenuHomeSchine - Phabricator

Starmade | Shipped Version of Java will cause the game to fail Launching, due to lack of valid SSL/HTTPS Certificate.
Closed, RejectedPublic

Description

The shipped Version of Java-7 that I got 3-4 weeks ago with the Launcher does not have the capability to Launch StarMade anymore due to lacking SSL Certificates or the ability to update said Certificates automatically. (aka Game Crashes silently before even starting up)

I changed the used Bin of Java in the Launcher to the Java-8 Install that is already on my Windows-8 Computer and it works fine, so it is not the OS specific SSL Certificate Mechanism that fails here, but the bundled Java-7's Certificates that does.

This Issue happened in the night from the 26th to the 27th of March 2018 (German Timezone) in case that info is any relevant to the Issue.

Details

Task Type
Bug
Testing Results
Affected Gamemode(s)
Launcher
Reproducible
uncertain
Last tested (version)
0.200.334
Category
Launcher
Hardware/Software/System
OS-Specific
No
Hardware-Specific
No
Video Card Vendor
uncertain
Steps to reproduce

I started the game at around 1:00am just fine, then I got an internet hickup in multiplayer, so I had to restart the game at around 2:45am

But it did not work anymore and couldn't even startup the Launcher itself for a solid 15 minutes despite having rebooted the entire Computer inbetween to try to fix it (and to clear any Ghostly instances of Java that might have been invisible in the Task Manager).

After those 15 minutes, the Launcher just started to work again all of a sudden. (that might be worth a Bug Report in on itself, but it might have been a connection issue, so I gonna let that slide).

But the Game itself crashed on Startup from now on (see Log below), until I finally decided to set the Launcher to use my Java-8 Install.

Interestingly there is no "Insert Logs" Field in this Bug Report Form, nor any way to attach stuff so I will put that here.

[2018-03-27 03:03:37] [VERSION] loading version from install dir: .\
[2018-03-27 03:03:37] [VERSION] VERSION: 0.200.334
[2018-03-27 03:03:37] [VERSION] BUILD: 20180203_224457
[2018-03-27 03:03:37] #### StarMade ##### [2018-03-27 03:03:37] # version 0.200.334 - build 20180203_224457 # [2018-03-27 03:03:37] ###########
[2018-03-27 03:03:37] [SERIAL] "not retrieved"
[2018-03-27 03:03:37] [INSTALLATION_DIRECTORY] "C:\StarMade\StarMade\."
[2018-03-27 03:03:37] [JVM-ARGUMENTS] [-Djava.net.preferIPv4Stack=true, -Xmn128M, -Xms512M, -Xmx4096M, -Xincgc]
[2018-03-27 03:03:37] [TEXTURE-PACK] WARNING: ignoring lava.png: not a directory
[2018-03-27 03:03:37] [TEXTURE-PACK] WARNING: ignoring lava.png.zip: not a directory
[2018-03-27 03:03:37] [TEXTURE-PACK] WARNING: ignoring shield_tex.png: not a directory
[2018-03-27 03:03:37] [TEXTURE-PACK] WARNING: ignoring shield_tex.png.zip: not a directory
[2018-03-27 03:03:37] [TEXTURE-PACK] WARNING: ignoring lava.png: not a directory
[2018-03-27 03:03:37] [TEXTURE-PACK] WARNING: ignoring lava.png.zip: not a directory
[2018-03-27 03:03:37] [TEXTURE-PACK] WARNING: ignoring shield_tex.png: not a directory
[2018-03-27 03:03:37] [TEXTURE-PACK] WARNING: ignoring shield_tex.png.zip: not a directory
[2018-03-27 03:03:37] [STARTER] AUTH TOKEN SUBMITTED VIA ARGUMENT
[2018-03-27 03:03:37] [API-LOGIN] REQUESTING OWN INFO
[2018-03-27 03:03:38] javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[2018-03-27 03:03:38] at sun.security.ssl.Alerts.getSSLException(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.Handshaker.processLoop(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.Handshaker.process_record(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
[2018-03-27 03:03:38] at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
[2018-03-27 03:03:38] at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
[2018-03-27 03:03:38] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
[2018-03-27 03:03:38] at java.net.HttpURLConnection.getResponseCode(Unknown Source)
[2018-03-27 03:03:38] at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)
[2018-03-27 03:03:38] at org.schema.game.common.api.ApiOauthController.a(SourceFile:136)
[2018-03-27 03:03:38] at org.schema.game.common.api.ApiOauthController.a(SourceFile:153)
[2018-03-27 03:03:38] at obfuscated.baL.a(SourceFile:54)
[2018-03-27 03:03:38] at org.schema.game.common.Starter.main(SourceFile:841)
[2018-03-27 03:03:38] Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[2018-03-27 03:03:38] at sun.security.validator.PKIXValidator.doBuild(Unknown Source)
[2018-03-27 03:03:38] at sun.security.validator.PKIXValidator.engineValidate(Unknown Source)
[2018-03-27 03:03:38] at sun.security.validator.Validator.validate(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source)
[2018-03-27 03:03:38] at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
[2018-03-27 03:03:38] ... 17 more
[2018-03-27 03:03:38] Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[2018-03-27 03:03:38] at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source)
[2018-03-27 03:03:38] at java.security.cert.CertPathBuilder.build(Unknown Source)
[2018-03-27 03:03:38] ... 23 more

Event Timeline

SmilingDemon claimed this task.

try .335 please

and you do add stuff by drag and drop the file to be added into here

SmilingDemon shifted this object from the S1 Public space to the S3 Starmade space.Mar 27 2018, 8:32 AM
SmilingDemon changed the visibility from "Custom Policy" to "Public (No Login Required)".
SmilingDemon changed the edit policy from "Task Author" to "Starmade (Project)".
SmilingDemon changed the task status from Open to Feedback.
SmilingDemon lowered the priority of this task from Normal to Trivial.
Restricted Application added a project: Waiting on Author. · View Herald TranscriptMar 27 2018, 8:32 AM

Will that work properly when joining a .334 Server, or do I have to Bug the admin to update ASAP?

Restricted Application edited projects, added Customer responded; removed Waiting on Author. · View Herald TranscriptMar 27 2018, 11:16 AM
Restricted Application changed the task status from Feedback to Open. · View Herald Transcript

different version numbers do not work with each other

question is however .. is it working with .335 apart from not being able to join a .334 Server ?

It fixed it for me, I am using the shipped Java 7 again after the Admin updated to 335. ^^

SmilingDemon closed this task as Rejected.Mar 29 2018, 7:34 AM

-rejected-

i thought so ;)
rejecting this then

Does this Bugtracker not have a "Fixed" State? "Rejected" sounds like "This has never been a Bug, now go fuck yourself" to say it as rudely as possible, lol.

Lets hope this reply doesnt auto-re-open the issue XD

lancake added a subscriber: lancake.Apr 1 2018, 3:32 PM

Does this Bugtracker not have a "Fixed" State? "Rejected" sounds like "This has never been a Bug, now go fuck yourself" to say it as rudely as possible, lol.
Lets hope this reply doesnt auto-re-open the issue XD

It has a specific "Closed" status which is what we use as "Fixed" but we only use that for tasks that went through the full cycle as only they got proper testing from start to finish. Tasks that never got in queue and/or were fixed along the way before it was even tested properly, just get rejected as we don't have as much confidence in it if it was completely fixed or not.

We definitely did not mean to deny that it was ever a bug. Even the "Closed" tasks may not be fully fixed as it's easy enough to overlook something during testing.
Sometimes we're also inconsistent with the usage of "Rejected", "Duplicate" and "Closed" status. In the end they all belong to the "Closed" tasks which is the only thing that matters for us, and is also why we don't care too much about which specific status is used.