Error occurring when trying to create the squadron in X-Wing, when clicking on the “2.0 Squad Spawn” button.
Attachment you can see the log created in the file: errorLog.txt
In addition, I can see this error when starting Vassal with Java from cmd console:
[i]
Error: java.security.cert.CertificateException: No name matching raw.githubusercontent.com found
Unhandled error parsing remote json:
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No name matching raw.githubusercontent.com found
I/O Error: java.security.cert.CertificateException: No name matching raw.githubusercontent.com found
Unhandled error parsing remote json:
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No name matching raw.githubusercontent.com found
Hello,
I have a problem with “squad spawn” too. Maybe you can help us.
I will try from my house (same wifi) with 2 computer (win7 and win 10).
The Problem: When I push the button of Squad spawn 2.0 nothing happens and appair a bug message.
Im trying to reinstale vassal and mod but dont work.
Vassal version: 3.2.17
Module version: 8.7.1
Message when I open the new game:
Error: can’t connect online to verify the module’s integrity with xwing-data2 - will attempt to use local files instead.
— File not found ‘manifest.json’ not found in C:\Users\jalgarra\Documents\Vassal\xwd2.zip
XWS2Upgrades line 343 - couldn’t load the manifest for upgrades
XWS2Upgrades line 343 - couldn’t load the manifest for conditions
XWS2Upgrades line 323 - couldn’t load the manifest for conditions
Star Wars X-Wing Miniatures Game version 8.7.1
Welcome to the VASSAL server
Message when I try to open my squad:
EEEk! A bug!
VASSAL had an internal error
VASSAL had an internal error. You can help the VASSAL developers fix it by sending them this error report with a description of what you were doing when the error happened.
If you’re not using the current version of the module, try that. If you are using the current version of the module, then you may wish to contact the maintainer of the module about the problem.
This bug was reported by a few users over the last year - it’s in all likelihood related to where you decided to place your module file, in a folder which isn’t giving file writing rights to the vassal module. In order for autospawn to work fast, it needs to download and occasionally refresh some local files where the module is.