[GH-ISSUE #5491] [bug]: Multiple Issues Affecting Usability in Web and Desktop Versions #2107

New issue

Open

opened 2026-03-16 23:13:15 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 23:13:15 +03:00

Owner

Originally created by @y0d4a on GitHub (Oct 17, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5491

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Web App

Browser

Chrome

Operating System

macOS

Bug Description

We’ve encountered several recurring issues while using Hoppscotch, both in the web and desktop apps.
I’m listing below the problems we’ve observed so far:

CORS Errors:
Tested extension, tested local proxy, nothing..
Workspace Sync:
Workspaces are not syncing between app and web (stuck in loading).
Console Errors
There are multiple console errors appearing even during normal operation.
Session Expiration Behavior
If a user is logged in and tries to import, edit environments, or collections, the session expires abruptly.
The only workaround is to log out and perform these actions while logged out
Shortcuts Not Working Consistently
Keyboard shortcuts intermittently stop working.
Reported by multiple users.
Sometimes they work after restarting the app..
Proxy Connection Fails
The proxy feature doesn’t seem to send any requests to the proxy server.
No connection attempt is visible in network or proxy logs.
We verified that network and firewall settings are not blocking it ...

Environment:
Desktop app (latest version, macOS)
Web app (latest Chrome)
Logged-in users via google account
Self-hosted instance

Originally created by @y0d4a on GitHub (Oct 17, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5491 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Web App ### Browser Chrome ### Operating System macOS ### Bug Description We’ve encountered several recurring issues while using Hoppscotch, both in the web and desktop apps. I’m listing below the problems we’ve observed so far: 1. CORS Errors: Tested extension, tested local proxy, nothing.. 2. Workspace Sync: Workspaces are not syncing between app and web (stuck in loading). 3. Console Errors There are multiple console errors appearing even during normal operation. <img width="1024" height="241" alt="Image" src="https://github.com/user-attachments/assets/f084aae6-f981-4f13-90b5-79dd9debb14c" /> 4. Session Expiration Behavior If a user is logged in and tries to import, edit environments, or collections, the session expires abruptly. The only workaround is to log out and perform these actions while logged out 5. Shortcuts Not Working Consistently Keyboard shortcuts intermittently stop working. Reported by multiple users. Sometimes they work after restarting the app.. 6. Proxy Connection Fails The proxy feature doesn’t seem to send any requests to the proxy server. No connection attempt is visible in network or proxy logs. We verified that network and firewall settings are not blocking it ... Environment: Desktop app (latest version, macOS) Web app (latest Chrome) Logged-in users via google account Self-hosted instance

kerem added the

bug

need testing

labels

2026-03-16 23:13:15 +03:00

kerem commented

2026-03-16 23:13:26 +03:00

Author

Owner

@roopepaajanen commented on GitHub (Oct 21, 2025):

We're facing similar issues with our self hosted version 2025.9.2 and 2025.9.1.
Additionally, we have noticed that changing between environment files containing secrets (Authorization header in this case) does not reflect in the sent request in web client. in this setup the request is set to inherit it's auth header from collection, which is set to use env value with <> variable.

In Desktop app most of the functionality works, but here is a list of failing functions:

Creating a new environment file returns "Session expired. Please log in again."
Changes made to environment files are not visible in browser client.
Fetching secret values from environment files.
Even though the UI fails, the plugin:relay|execute returns success 200.

@roopepaajanen commented on GitHub (Oct 21, 2025): We're facing similar issues with our self hosted version 2025.9.2 and 2025.9.1. Additionally, we have noticed that changing between environment files containing secrets (Authorization header in this case) does not reflect in the sent request in web client. in this setup the request is set to inherit it's auth header from collection, which is set to use env value with <<token>> variable. In Desktop app most of the functionality works, but here is a list of failing functions: - Creating a new environment file returns "Session expired. Please log in again." - Changes made to environment files are not visible in browser client. - Fetching secret values from environment files. - Even though the UI fails, the plugin:relay|execute returns success 200.

kerem commented

2026-03-16 23:13:31 +03:00

Author

Owner

@roopepaajanen commented on GitHub (Oct 22, 2025):

Rollbacking to version 2025.8.1 is also failing. Rollbacking and executing database migration seems to set all request in non-personal workspaces on default values with title "Untitled" with request url "https://echo.hoppscotch.io". Additionally, I am getting the following error message on UI when opening the app: "Schema validation failed for persistence. v1:restCollections. A backup has been created with suffix '-backup'"
Rollbacking back to 2025.9.1 restores the files, however the earlier mentioned errors are back.

@roopepaajanen commented on GitHub (Oct 22, 2025): Rollbacking to version 2025.8.1 is also failing. Rollbacking and executing database migration seems to set all request in non-personal workspaces on default values with title "Untitled" with request url "https://echo.hoppscotch.io". Additionally, I am getting the following error message on UI when opening the app: "Schema validation failed for persistence. v1:restCollections. A backup has been created with suffix '-backup'" Rollbacking back to 2025.9.1 restores the files, however the earlier mentioned errors are back.