# Verse Language Server disconnects when running a Verse script 

**URL:** <https://forums.unrealengine.com/t/verse-language-server-disconnects-when-running-a-verse-script/2733503>\
**Category:** Verse\
**Tags:** unreal-engine, unreal-editor-for-fortnite, editor, question, fortnite\
**Created:** [July 4, 2026, 1:02pm UTC](https://forums.unrealengine.com/t/verse-language-server-disconnects-when-running-a-verse-script/2733503 "2026-07-04T13:02:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![APX\_Lenzi](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@APX\_Lenzi](https://forums.unrealengine.com/u/APX_Lenzi)\
**Post date:** [July 4, 2026, 1:02pm UTC](https://forums.unrealengine.com/t/verse-language-server-disconnects-when-running-a-verse-script/2733503/1 "2026-07-04T13:02:18Z")

</div>

**Verse Language Server disconnects when running a Verse script**

Hi,

I’m having an issue with the Verse extension. Whenever I run a Verse script, I get the following error in VS Code:

```verse
[Error - 2:25:03 PM] Connection to server is erroring. Shutting down server.

```

 ![Screenshot 2026-07-04 144335](https://d3kjluh73b9h9o.cloudfront.net/original/4X/b/3/8/b381397033046270639757daea09f7b94b560748.png)

After this happens, the Verse extension stops working completely (no syntax highlighting, autocomplete, or other language features).

Has anyone experienced this issue before or knows how to fix it?

Thanks!

---

<div class="post-metadata">

**Author:** ![Boschkoo](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/boschkoo/32/1198267_2.png) [@Boschkoo](https://forums.unrealengine.com/u/Boschkoo)\
**Post date:** [August 18, 2026, 6:53am UTC](https://forums.unrealengine.com/t/verse-language-server-disconnects-when-running-a-verse-script/2733503/2 "2026-08-18T06:53:33Z")

</div>

That error is the Verse language server dying when UEFN compiles. VS Code then drops highlighting and IntelliSense until you restart the server. Common, not a bad script.

Do this in order:

1. In VS Code: Command Palette → `Verse: Restart Language Server` (or Developer: Reload Window).
2. Close extra VS Code windows. One window on the UEFN project is enough. Two instances fighting over the same `.verse` digest will crash the LS.
3. Don’t “Run” the Verse file from VS Code. Compile / Push Changes from UEFN. The LS is not a runtime.
4. If it still dies on every compile: quit UEFN and VS Code, delete the local Verse cache under your project (`Binaries`, `.vs`, and the generated `*.digest.verse` is fine — it comes back on compile), start **UEFN first** , then open the project in VS Code.
5. Update the official Verse extension. An old LS against a new UEFN build is a frequent cause of `Connection to server is erroring`.

If it only happens on one device: look at the Verse output panel for the line _before_ the shutdown. A parse error in a huge module, or a path with non-ASCII characters, will take the LS down with it. Fix that file and the disconnects stop.
