License Error when Running Wolfram Engine 14 with WLJS about wolfram-js-frontend

[pyreymo]

2minutesLog.txt

Windows 11
WLJS.Notebook.Setup.2.3.5.exe

[pyreymo]

It seems to work without any errors, the ball follows the mouse to create and then moves normally after I checked "Gravity".

This file Balls.log shows all the displays after I run Examples/Balls/Balls.wls.

[JerryI]

Hello @pyreymo,
We are sorry about that, it looks like a bug. We have seen before, that sometimes Wolfram Engine does not allow to run 2 instances on the same machine for no reason (WLJS requires exactly 2), but quite rare.

We will prepare a test script for you to diagnose a problem and will try our best to help you :)

PS: thank you for log file

[JerryI]

Could you, please, try to download this repo and run the following demo (just directly by double-click) ?

Examples/Balls/Balls.wls

And after it finishes an installation, open http://127.0.0.1:8010 page in the browser.

[JerryI]

Looks great! One branch less..
Could you, please, locate a folder C:\\Users\<YourName>\AppData\Roaming\wljs-notebook

then you need to copy a file _settings.wl (here is a Gist link) there. It will disable second Wolfram Kernel on the startup, if it causes the crash.

Check if it crashes again and if possible, we would be appreciated for a log file as well.

[pyreymo]

I edited my _settings.wl to <|"Autostart" -> False|> and restarted the WLJS launcher. However, I am still encountering the license error, though it appears slightly different this time.

Here is the full log:
Launcher.log

[JerryI]

If you still have motivation, I would like to ask you to do a few more tricks. You are helping us a lot and other users, who could face similar issues.

If not - it is fine, we don't want to steal your time. Thank you again.

Tricks (just in case)
Since it fails at Autotest, could you please edit the file

C:\\Users\<YourName>\AppData\Roaming\wljs-notebook\Scripts\start.wls

and delete following lines

It will bypass an autotest and we might see some reasonable answer and which part of a stack is malfunctioning.