It's not a network issue. I've checked everything and it's still like this.

Cchenmiki · 21 Jan

Spine Launcher 4.2.19
Esoteric Software LLC (C) 2013-2024 | http://esotericsoftware.com
Windows 7 Ultimate amd64 6.1
WARNING: Unable to ping server: eu.esotericsoftware.com
javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at sun.security.ssl.SSLSocketImpl.handleEOF(Unknown Source)
at sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.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.https.HttpsURLConnectionImpl.connect(Unknown Source)
at s.EPE.(:161)
at java.lang.Thread.run(Unknown Source)
Cause: [eof] SSL peer shut down incorrectly
at sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)
at sun.security.ssl.SSLTransport.decode(Unknown Source) ...
NVIDIA Corporation, GeForce GTX 1050 Ti/PCIe/SSE2, 4.6.0 NVIDIA 441.08
WARNING: Unable to ping server: jp.esotericsoftware.com
[net.Socket] Connection reset
at sun.nio.ch.NioSocketImpl.implRead(Unknown Source)
at sun.nio.ch.NioSocketImpl.read(Unknown Source)
at sun.nio.ch.NioSocketImpl$1.read(Unknown Source)
at java.net.Socket$SocketInputStream.read(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)
at sun.security.ssl.SSLTransport.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.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.https.HttpsURLConnectionImpl.connect(Unknown Source)
at s.EPE.(:161)
at java.lang.Thread.run(Unknown Source)
WARNING: Unable to ping server: us.esotericsoftware.com
[net.Socket] Connection reset
at sun.nio.ch.NioSocketImpl.implRead(Unknown Source)
at sun.nio.ch.NioSocketImpl.read(Unknown Source)
at sun.nio.ch.NioSocketImpl$1.read(Unknown Source)
at java.net.Socket$SocketInputStream.read(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)
at sun.security.ssl.SSLTransport.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.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.https.HttpsURLConnectionImpl.connect(Unknown Source)
at s.EPE.(:161)
at java.lang.Thread.run(Unknown Source)
ERROR: Unable to authenticate activation code: 已建立连接，但未连接到预期的服务器。
[error] Unable to connect to server: https://usapi.esotericsoftware.com:443
at s.zDv.(:275)
at s.zDv.S(:128)
at s.ofY.S(:277)
at s.gXJ.(:285)
at s.gXJ.S(:163)
at s.zxa.I(:107)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Cause: javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at sun.security.ssl.SSLSocketImpl.handleEOF(Unknown Source)
at sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.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.https.HttpsURLConnectionImpl.connect(Unknown Source)
at s.zDv.(:256) ...
Cause: [eof] SSL peer shut down incorrectly
at sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)
at sun.security.ssl.SSLTransport.decode(Unknown Source) ...
ERROR: Unable to authenticate activation code: 已建立连接，但未连接到预期的服务器。
[error] Unable to connect to server: https://usapi.esotericsoftware.com:443
at s.zDv.(:275)
at s.zDv.S(:128)
at s.ofY.S(:277)
at s.gXJ.(:285)
at s.gXJ.S(:163)
at s.zxa.I(:107)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Cause: javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at sun.security.ssl.SSLSocketImpl.handleEOF(Unknown Source)
at sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.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.https.HttpsURLConnectionImpl.connect(Unknown Source)
at s.zDv.(:256) ...
Cause: [eof] SSL peer shut down incorrectly
at sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)
at sun.security.ssl.SSLTransport.decode(Unknown Source) ...
ERROR: Unable to authenticate activation code: 已建立连接，但未连接到预期的服务器。
[error] Unable to connect to server: https://usapi.esotericsoftware.com:443
at s.zDv.(:275)
at s.zDv.S(:128)
at s.ofY.S(:277)
at s.gXJ.(:285)
at s.gXJ.S(:163)
at s.zxa.I(:107)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Cause: javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at sun.security.ssl.SSLSocketImpl.handleEOF(Unknown Source)
at sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.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.https.HttpsURLConnectionImpl.connect(Unknown Source)
at s.zDv.(:256) ...
Cause: [eof] SSL peer shut down incorrectly
at sun.security.ssl.SSLSocketInputRecord.read(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.readHeader(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)
at sun.security.ssl.SSLTransport.decode(Unknown Source) ...

Spinebot · 21 Jan

The issue you're experiencing with Spine not being able to connect to the servers and the SSL handshake errors could be related to network configurations that interfere with SSL connections. This might include firewalls, proxies, or network security settings that perform deep packet inspection or block self-signed certificates. Even if you've checked your network settings, it's possible that some configurations, such as SSL inspection or proxy settings, are still affecting the connection. You might want to try connecting through a different network, such as a mobile hotspot, to see if the issue persists. Additionally, ensure that your network allows connections to the Spine servers and that no security software is blocking these connections.

Nate · 21 Jan

已建立连接，但未连接到预期的服务器
Connection established, but not to expected server

This error means something has intercepted the connection to the Spine server. For example, if you are using WIFI or a proxy that requires login, any time you go to a web page, you are given the WIFI login page instead. It can also happen if your network configuration gives its own error page instead of allowing the communication to reach the Spine server. Some networks are configured to do that when they don't like the communication for some reason, like the site is blocked or they don't like the certificate a site is using. Spine's servers use a self signed certificate which makes sense because Spine server's are for a desktop app, not a browser. It makes sense for a network to block such a certificate for a browser, but Spine is not a browser and an exception should be made. Spine servers reject being visited using a browser.

I know you said you checked everything and you don't believe it's your network, but it's pretty clearly something with your network configuration, ISP, or somewhere else between you and the Spine server that is preventing communication. It could be a hardware or software firewall or other software, like anti-malware or antivirus software. Whatever it is, it's stopping communication from reaching Spine's servers.

Can you connect to a different network and try again? For example, a coffee shop WIFI or a friend's house or at home if you are at work. If that works, then it's definitely the network you were using before. If it doesn't work, it may indicate that the problem is the configuration or software on your computer.

KKatana · 2 Feb

Same issue here. I've seen similar posts in forum(https://esotericsoftware.com/forum/d/27942-spine%E9%87%8D%E6%96%B0%E5%AE%89%E8%A3%85%E6%97%A0%E6%B3%95%E6%BF%80%E6%B4%BB/13) and could not find a solution, they all happen recently and are all located in China. In my case, I've been using spine in the same environment for more than 1 year without an issue, but I do not open it for 2 months until today and this issue pop up. I did not change my network configuration for quite a long time. Here is the log:
WARNING: Unable to ping server: jp.esotericsoftware.com
[net.Socket] Connection reset by peer
at sun.nio.ch.NioSocketImpl.implWrite(Unknown Source)
at sun.nio.ch.NioSocketImpl.write(Unknown Source)
at sun.nio.ch.NioSocketImpl$2.write(Unknown Source)
at java.net.Socket$SocketOutputStream.write(Unknown Source)
at sun.security.ssl.SSLSocketOutputRecord.flush(Unknown Source)
at sun.security.ssl.HandshakeOutStream.flush(Unknown Source)
at sun.security.ssl.ClientHello$ClientHelloKickstartProducer.produce(Unknown Source)
at sun.security.ssl.SSLHandshake.kickstart(Unknown Source)
at sun.security.ssl.ClientHandshakeContext.kickstart(Unknown Source)
at sun.security.ssl.TransportContext.kickstart(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.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.https.HttpsURLConnectionImpl.connect(Unknown Source)
at s.EPE.(:161)
at java.lang.Thread.run(Unknown Source)
WARNING: Unable to ping server: us.esotericsoftware.com
[net.Socket] Connection reset by peer
at sun.nio.ch.NioSocketImpl.implWrite(Unknown Source)
at sun.nio.ch.NioSocketImpl.write(Unknown Source)
at sun.nio.ch.NioSocketImpl$2.write(Unknown Source)
at java.net.Socket$SocketOutputStream.write(Unknown Source)
at sun.security.ssl.SSLSocketOutputRecord.flush(Unknown Source)
at sun.security.ssl.HandshakeOutStream.flush(Unknown Source)
at sun.security.ssl.ClientHello$ClientHelloKickstartProducer.produce(Unknown Source)
at sun.security.ssl.SSLHandshake.kickstart(Unknown Source)
at sun.security.ssl.ClientHandshakeContext.kickstart(Unknown Source)
at sun.security.ssl.TransportContext.kickstart(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.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.https.HttpsURLConnectionImpl.connect(Unknown Source)
at s.EPE.(:161)
at java.lang.Thread.run(Unknown Source)

My spine version is 4.2.19.
What I've tried:
1.ping using cmd.exe or powershell. Ping is success but some packets are lost(0₅₀%)
2.Using VPN. Not work
3.Upgrade to latest spine. Not work
4.Connect to other hot spot. Not work

KKatana · 2 Feb

I've fixed my problem. In my case, the connection is blocked by Kaspersky. But I'm still don't know why this happens as I've been using Kaspersky for years. My other app works fine except Spine, hopefully developers can figure it out and give me some advices. I dont want to close Kaspersky every time when Spine needs the network connection

Misaki · 3 Feb

Katana I am glad you were able to find the cause.

I hate to say this, but we have no way to prevent false positives from anti-virus software, including Kaspersky. We are in regular contact with 50+ software vendors such as Avast, Avira, BitDefender, Kaspersky, McAfee, Norton, and Symantec to resolve the false positives they report for our software. However, they are constantly updating their heuristics, and we are constantly updating our software, so there are times when Spine will run fine with that anti-virus software enabled, but will not run after the update. This can happen on a daily basis.
Despite the frequency of these issues, communicating with these vendors is usually very time consuming. In the end, the quickest solution we can suggest to users is to temporarily disable their anti-virus software.