The Verse Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.

I’m so tired of this problem, anybody else have it? Know how to make it stop crashing? This is the error I see in VBScript EVERY SINGLE DAY… hate it. Have to close down VB and then reopen the file from UEFN.

“The Verse Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.”

2 Likes

I’ve been using Verse daily for the last month and never got it.

When I was using Wi-Fi (good Wi-Fi 400+ MBPS) I would disconnect (log out from Epic) all the time. I gave up and ran a wire across my house from my PC to router and the problems stopped.

Fortnite does a hint pretty often: “Use a wired connection for best results” or something similar. It seems (to me) that UEFN does not play well with Wi-Fi.

I appreciate that, I have a wired connection. The verse language server runs off of node.js I believe. Not even a reason to have a network connection I think.

1 Like

Good luck, but at least you know that it’s not a universal issue!

1 Like

Agreed, thanks for the response for sure!

1 Like

I have that too, did you get it away? I’ve been looking for a solution for 3 days and can’t find anything

1 Like

Have you tried disabling extensions? There is a tool that can help: Visual Studio Code extension bisect utility

Reinstalling might be worth a shot.

Or if you want to live on the edge:

There is Verse code that is capable of generating this error, so not necessarily a system issue. Several crash reports have been generated and once I removed the code, the error goes away. To isolate this, I just created a default Verse device with the default Hello World code, compiled and ran it, and there was no issue. But when I tried to use this particular section of code, I got the exact same message. When I removed the section of code, the error immediately went away. Another option is to try and comment out various sections of the Verse code and see if that makes the error go away.

Still having this problem every time I boot up VS code February 2025, my project has a ton of Verse script so I haven’t found if there’s a broken section yet but this error makes it impossible to do so because there are no error markings.

Just build verse code before launching VS code. Solved this error for me.

Thanks