[BUG] After the update, the panel cannot be opened

[containmethod]

OmniRoute Version

3.7.8

Installation Method

npm (global)

Operating System

Windows

OS Version

Windows 11 25H2

Node.js Version

v22.22.2

Provider(s) Involved

No response

Model(s) Involved

No response

Client Tool

No response

Description

This is the second time when updating the command npm install -g omniroute@latest I'm getting this error. A screenshot of a window that doesn't respond to anything. The button doesn't work, nothing happens. I can't log in. Last time, the only thing that helped was deleting the database in C:\Users\User\ .omniroute storage.sqlite and reinstalling. Then it worked. But I lost all my keys.

Now I can't afford to lose all my keys and proxies again. Fix the problem, is it in your database, or am I unaware of the cause? But I can't update properly and don't understand how to do it. What should I do now?

Steps to Reproduce

npm install -g omniroute@latest

error -

The button "Start Onboarding" doesn't respond to any actions, it's impossible to enter the program.

This error is happening twice. I thought last time the problem was that the version was too old. But this time I updated from version 3.7.1 and the error happened again. Everything was working fine before the update.

Expected Behavior

successful update

Actual Behavior

Unable to open omniroute

Test Impact

Needs a new unit test

Error Logs / Output

Screenshots

No response

Additional Context

No response

Validation Plan

No response

[kilo-code-bot]

This issue appears to be a duplicate of #1115.

[BUG] I installed but it doesn't work (#1115)

Similarity score: 90%

This comment was generated by Kilo Auto-Triage.

[iamzycao-png]

i got this issue too.. i downgrade to 3.7.7

[containmethod]

i got this issue too.. i downgrade to 3.7.7

I chose to install a specific version. I launched version 3.7.7, but all my previous accounts and proxies disappeared. This isn't a solution. It's just a complete cleanup before installation. This isn't how an update is supposed to work; all my data disappeared.

[diegosouzapw]

Hi there! The issue description provided is completely empty. Could you please provide more context on what you mean by "the panel cannot be opened"? Specifically, please include any error logs, what browser/device you are using, and steps to reproduce the issue. Thank you!

[containmethod]

Hi there! The issue description provided is completely empty. Could you please provide more context on what you mean by "the panel cannot be opened"? Specifically, please include any error logs, what browser/device you are using, and steps to reproduce the issue. Thank you!

I'm using the latest version of Chrome. There are no errors, just this window that opens and doesn't respond to anything. Nothing clicks or happens. I can't log in to the dashboard. What's shown on the screenshot opens, and nothing else happens. This window just hangs there and doesn't respond to anything. When I launch OmniRoute, a window opens as in the screenshot http://localhost:20128/login and then nothing else works or happens.

I run the command

npm install -g omniroute@latest

and this problem occurs. The dashboard stops opening and doesn't respond at all.

Then I ran the command as recommended in the comments:

npm install -g omniroute@3.7.7

The dashboard opened normally, but all my data was deleted. Everything was completely cleared out, even though I added providers and proxies. The problem is specifically with your database; updates break it and it stops logging in properly. This is the second time this has happened to me, only this time I lost important logged-in accounts.

[containmethod]

Updates work fine with a blank version. But if I've added providers and proxies, that's it, updates don't work. They don't transfer. Every time I update, I have to delete and clean everything. Updating with data preservation doesn't work.

[containmethod]

I made a copy of the folder C:\Users\User\.omniroute

I ended up rolling back to version 3.7.1, restoring the data, and everything opened and loaded fine.

This is terrible, I can't update now. The same error happened twice. I won't update again unless you update properly and preserve the data.

[diegosouzapw]

Thank you for the detailed report. You took the correct action by rolling back to v3.7.1 and restoring your .omniroute folder for now. We are actively investigating an issue with the SQLite database path migration on Windows installations during updates, which can cause the app to lose track of the existing credentials. Please stay on v3.7.1 while we address this for the upcoming v3.8.0 LTS release.

[Akter39]

First install. 2 reload install. Button "Start onboarding" not work. (last Chrome and Firefox)
Sometimes errors occur:
Uncaught (in promise) TypeError: Failed to fetch
at sw.js:62:16
at sw.js:89:7
5login:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Sometimes:
4login:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Sometimes:
Content Security Policy of your site blocks the use of 'eval' in JavaScript`
The Content Security Policy (CSP) prevents the evaluation of arbitrary strings as JavaScript to make it more difficult for an attacker to inject unathorized code on your site.

To solve this issue, avoid using eval(), new Function(), setTimeout([string], ...) and setInterval([string], ...) for evaluating strings.

If you absolutely must: you can enable string evaluation by adding unsafe-eval as an allowed source in a script-src directive.

⚠️ Allowing string evaluation comes at the risk of inline script injection.

1 directive
Source file location Directive Status
7173-4cef51d1a3312939.js:1 script-src blocked
Read more: Content Security Policy – ​​assessment

But most often there are no errors. The button simply doesn't respond.

[diegosouzapw]

This issue has been identified as a database path migration problem on Windows. The fix preserves the legacy ~/.omniroute folder location for existing installations to prevent data loss. The patch is now merged in the release/v3.8.0 branch and will be deployed in the final v3.8.0 release.