• EditorBugs
  • Can't run the software offline

Hello to the wonderful SPINE TEAM,

Dont know why i cant use spine offline.
Thanks for your answer.

<3
With love

Spine Launcher 4.2.18
Esoteric Software LLC (C) 2013-2024 | http://esotericsoftware.com
Windows 10 Pro N amd64 10.0
NVIDIA Corporation, NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2, 4.6.0 NVIDIA 561.09
ERROR: Unable to start (0x137438953472): Unable to reach the server (unknown host).
[error] Unable to connect to server: https://jpapi.esotericsoftware.com:443
   at s.tTm._(_:275)
   at s.tTm.F(_:128)
   at s.soV.F(_:277)
   at s.yQC._(_:285)
   at s.yQC._(_:169)
   at s.nvs.I(_:48)
   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: [net.UnknownHost] jpapi.esotericsoftware.com
   at sun.nio.ch.NioSocketImpl.connect(Unknown Source)
   at java.net.SocksSocketImpl.connect(Unknown Source)
   at java.net.Socket.connect(Unknown Source)
   at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
   at sun.net.NetworkClient.doConnect(Unknown Source)
   at sun.net.www.http.HttpClient.openServer(Unknown Source)
   at sun.net.www.http.HttpClient.openServer(Unknown Source)
   at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
   at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
   at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
   at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source)
   at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
   at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
   at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source)
   at s.tTm._(_:256) ...
Related Discussions
...

Hello,

It seems you're having trouble running Spine offline. Based on the information provided, here are a few steps you can take to resolve the issue:

  1. Reinstall Spine: Sometimes, reinstalling Spine with the latest launcher from your License Page can resolve connectivity issues. This is especially important if there was a certificate expiration or other updates that need to be applied.

  2. Check Firewall/Antivirus Settings: Ensure that your firewall or antivirus software is not blocking Spine. You may need to add exceptions for Spine in your firewall or antivirus settings.

  3. Network Configuration: If you are behind a proxy or firewall, ensure that it allows connections to Spine servers. You can refer to the Proxy server - Spine User Guide for more details.

  4. Spine Log File: If the above steps do not resolve the issue, please check your spine.log file for more detailed error messages. You can find the log file as described here: Spine Troubleshooting: spine.log.

  5. Different Network: Try running Spine on a different network, such as a mobile hotspot, to see if the issue is related to your current network configuration.

If you continue to experience issues, please provide the spine.log file for further analysis.

With love,
The Spine Team

Are you running Spine in a VM? If so, please try running Spine natively. If not, Windows has a feature called VBS that runs apps virtualized, meaning Windows runs apps in a VM without you knowing it, and this causes problems with Spine running offline. To disable VBS you can turn off "SVM" in BIOS:

Image supprimée en raison de l'absence de support de HTTPS. | Afficher quand même

Turning off SVM should be sufficient. Otherwise VBS can be disabled in other ways, like this:

1) Run: Start > Run > gpedit.msc
2) Expand: Local Computer Policy > Administrative Templates > System > Device Guard
3) Double click: Turn On Virtualization Based Security
4) Set it to Disabled and click OK.
5) Reboot.

If you are running Windows 10 Home, you won't have gpedit.msc, which is the Group Policy Editor. There are some hacks to enable gpedit.msc (do an internet search).

Alternatively you can download and double click this registry file. That registry file is equivalent to doing this:

1) Run: Start > Run > regedit
2) Expand: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > DeviceGuard
3) On the right side: right click > New > DWORD (32-bit) Value
4) Name it EnableVirtualizationBasedSecurity with a value of 0.
5) Expand: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Lsa
6) On the right side: right click > New > DWORD (32-bit) Value
7) Name it LsaCfgFlags with a value of 0.
8) Reboot.

Once Spine is not running virtualized, it will run offline. Please note that Spine must be run online first so it can download specific editor versions, then it will run those versions offline.

    Nate Hey,

    Disbaled SVM in bios and it work like a charm.
    You are the best support i ever had to contact.
    Thank's