question: Internal Server Error after restarting OmniRoute on Windows

[muhammad-fiaz]

OmniRoute Version

3.8.49

Installation Method

npm (global)

Operating System

Windows

OS Version

No response

Node.js Version

v25.9.0

Provider(s) Involved

No response

Model(s) Involved

No response

Client Tool

No response

Description

I found a startup issue on Windows after installing OmniRoute via npm.

On a fresh installation, OmniRoute starts normally. The dashboard loads successfully and everything appears to work.

However, after stopping the server with Ctrl+C and starting it again by running omniroute, the dashboard no longer loads and instead displays an Internal Server Error.

Deleting the .omniroute directory allows OmniRoute to start successfully again, but the problem returns after stopping and restarting the server.

This appears to be different from the previously fixed upgrade issue because it happens on a completely fresh installation without upgrading from an older version.

Steps to Reproduce

1. Install OmniRoute globally:

   npm install -g omniroute

2. Run:

  omniroute

3. Wait until the dashboard opens successfully.

4. Stop the server using Ctrl+C.

5. Run:

  omniroute

6. Open the dashboard again.

7. Observe that the dashboard displays:

  Internal Server Error

8. Delete:

  C:\Users\<username>\.omniroute

9. Run omniroute again.

10. The dashboard works again until the server is stopped and restarted.

Expected Behavior

OmniRoute should start successfully every time it is run.

Stopping the server with Ctrl+C should shut it down cleanly without leaving it in a state that prevents future startups.

Running omniroute again should start the server normally, reuse the existing .omniroute data directory, and load the dashboard without displaying an Internal Server Error.

Users should not have to delete the .omniroute directory or reinstall OmniRoute to restore normal operation.

Actual Behavior

The first launch after a fresh installation works correctly.

After stopping OmniRoute with Ctrl+C and running omniroute again, the dashboard immediately displays Internal Server Error.

Deleting the .omniroute directory temporarily fixes the issue until the next restart.

Test Impact

Unsure

Error Logs / Output

No error or stack trace is printed in the terminal.

The first run starts successfully:

✔ OmniRoute is running!

After stopping the server with Ctrl+C and running `omniroute` again, the dashboard no longer loads and the browser displays:

Internal Server Error

Deleting the `.omniroute` directory allows OmniRoute to start successfully again, but the issue returns after stopping the server and running `omniroute` again.

Screenshots

Additional Context

• Installation method: npm global install
• Operating System: Windows 11 25H2
• Node.js: v25.9.0
• No proxy or custom network configuration.
• Configured providers: NVIDIA NIM and OpenRouter.
• This occurs on a completely fresh installation with a newly created .omniroute directory.
• The first launch works correctly and the dashboard loads successfully.
• After stopping the server with Ctrl+C and running omniroute again, the dashboard consistently displays Internal Server Error.
• Deleting the .omniroute directory temporarily resolves the issue, but it returns after the next restart.
• This issue is similar to previously reported startup/Internal Server Error issues, including fix(startup): Internal Server Error after upgrading from v3.8.44 to v3.8.45/v3.8.46 #6664, Omniroute Internal Server Error #6573, [BUG] Internal Server Error #4805, [BUG] Internal Server Error in webui when i start server in termux #2890, [BUG] Internal Server Error 3.7.2 #1704, and [BUG] Internal Server Error when opening a website #1616. Although the reproduction steps differ, the observed symptom is similar: the dashboard fails to load and displays Internal Server Error after restarting the server.

Validation Plan

Manual validation

npm install -g omniroute

omniroute

• Verify that the dashboard loads successfully.

Stop the server with Ctrl+C.

omniroute

• Verify that the dashboard loads successfully without displaying Internal Server Error.

Repeat the Ctrl+C → omniroute restart cycle multiple times.

Expected result

• OmniRoute starts successfully on every launch.
• The dashboard loads correctly after every restart.
• The existing .omniroute directory is reused without requiring deletion.
• No Internal Server Error is displayed after restarting the server.

[muhammad-fiaz]

hello @diegosouzapw is this resolved yet??

[diegosouzapw]

Hi @muhammad-fiaz! Thanks for reporting this. It was fixed in release/v3.8.50: Cadeia de fix de migrations na 3.8.50 (#9745, #9884, #9965, #9934, #10152) — aborts de colisão eliminados. Please upgrade and confirm. Closing as resolved.

[muhammad-fiaz]

@diegosouzapw when will it get released?

[diegosouzapw]

Hi @muhammad-fiaz — the fix for this is included in v3.8.50, which is the currently active release branch (pull request #8875 open) and has not been published to npm yet: the latest publicly available version on npm is 3.8.49.

The upstream migration-collision fix landed as a chain (#9745, #9884, #9965, #9934, #10152). Once v3.8.50 ships, run npm install -g omniroute@latest (or npm update -g omniroute) and restart — you should no longer hit the Internal Server Error on the second launch without deleting .omniroute.

I will leave this issue closed since the root cause is already resolved in the upcoming release. If you still see the error after upgrading to v3.8.50 once it is out, please reopen and we will dig deeper.