mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5541] [bug]: Instability in Self hosted Desktop app #2135
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2135
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @roopepaajanen on GitHub (Oct 31, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5541
Originally assigned to: @CuriousCorrelation on GitHub.
Is there an existing issue for this?
Platform
Desktop App
Browser
Chrome
Operating System
macOS
Bug Description
Hi,
We have been facing instability in our self hosted desktop app since the release of versions 2.9.x. We are facing the same issues in 2.10.0 which was released earlier today. In our browser client everything seems to be working normally.
Simply trying to create a new environment file returns an error
Session expired. Please log in again, but everything else continues to work. Pressing the "Create Environment" button triggers the following network logs:First: plugin:relaylexecute
Second: plugin:relaylexecute
I am wondering if the status message 403 in the second request is related to our issue.
Websocket failed
After keeping the desktop app idle after login for about one minute, the desktop returns error
WebSocket connection to 'wss://domain/graphql' failed: The operation couldn’t be completed. Socket is not connected.Database migration rollback to 2025.8.1 fails
Last somewhat working version for us is 2025.8.1, but we cannot execute database migration from 2025.9.x back to 2025.8.1. The migration turns every API request in non-personal collection into default values.
I'll paste our configuration below, any help would be much appreciated.
Kubernetes: v1.30.5 - amd64
Gateway
Virtualservice
Whitelist (long only for debugging reasons):
Deployment Type
Self-hosted (on-prem deployment)
Version
2025.10.0
@roopepaajanen commented on GitHub (Oct 31, 2025):
Additionally, here is application start logs, if they would happen to give any insight
@Pezhvak commented on GitHub (Nov 2, 2025):
My issue is with saving requests in desktop app, it constantly says "Session expired. Please log in again."
But I'm already logged in, even can see the changes that is made in the browser.
@roopepaajanen commented on GitHub (Nov 3, 2025):
Additionally, I noticed that creating a new environment before logging in worked normally. The issues is faced only after login. We are using Microsoft authentication.
@bnelissen-orisha commented on GitHub (Nov 3, 2025):
I have also the issue when I try to save.
In DevTools :
In container logs :
@rock-tran commented on GitHub (Nov 6, 2025):
I also face this issue. Confirmed that 2025.8.1 is working.
@Pezhvak commented on GitHub (Nov 8, 2025):
First the file upload broke, now this, every update some regression is happening, it seems updating is seriously risky.
@saviocamacam commented on GitHub (Nov 8, 2025):
I also face this issue.
@jamesgeorge007 commented on GitHub (Nov 10, 2025):
Thanks for the detailed report. We've identified the root cause, and the fix has been merged and is scheduled for the patch release this week. Really sorry about the trouble with this upgrade.
@caturbgs commented on GitHub (Nov 12, 2025):
Is there an estimated time of resolution for this issue? Since it has occurred on both the self-hosted desktop app and the web app within our organization.
@jamesgeorge007 commented on GitHub (Nov 12, 2025):
We’re currently addressing a few issues encountered in our release pipeline, and aim to release the patch later this week. We'll post an update here once it's live.
@jamesgeorge007 commented on GitHub (Nov 12, 2025):
Also, @caturbgs, could you elaborate on the issues encountered in the web app?
@caturbgs commented on GitHub (Nov 12, 2025):
Every time I open the collections, it always shows empty. This issue occurred on the same latest update that broke the desktop app.
@jamesgeorge007 commented on GitHub (Nov 12, 2025):
Can you open a separate issue to track this concern?
@nivedin commented on GitHub (Nov 12, 2025):
@caturbgs can you see if your cookie or session has expired when expanding the collection, can you check the network tab
@caturbgs commented on GitHub (Nov 12, 2025):
https://github.com/hoppscotch/hoppscotch/issues/5574
here's the new issue
@caturbgs commented on GitHub (Nov 12, 2025):
@liyasthomas commented on GitHub (Nov 13, 2025):
We’ve resolved this issue in the latest desktop release candidate, v2025.10.1. Please update to the latest version and let us know what you think.
@roopepaajanen commented on GitHub (Nov 13, 2025):
The latest version (2025.10.1) did indeed resolve the issue with creating environments in the Desktop client — thank you!
However, I’m still seeing the following error in the Desktop client console logs:
WebSocket connection to 'wss://domain/graphql' failed: The operation couldn’t be completed. Socket is not connected.This is the same WebSocket issue I mentioned in the original report.
That said, I have not noticed any visible impact on actual app functionality so far — at least nothing obvious.
@roopepaajanen commented on GitHub (Nov 25, 2025):
Hi again,
our windows users are facing the same issue with version 2025.10.1 - they are not able to create new environment files. They are getting the same error message
Session expired. Please log in again, as I received on previous versions on my mac.Are other people facing similar issues?
edit: Windows users are able to modify environment files, create collections, execute API requests. But simply are not able to create new environment files.
@CuriousCorrelation commented on GitHub (Nov 25, 2025):
@roopepaajanen That's quite strange since we haven't seen this in our Windows testing suite. There's a major update aimed to be release by the end of this month, it includes a few QoL improvements that may fix some tangential issues as well.
If that doesn't fix this, please feel free to create a new issue with any details you can provide especially desktop logs (anonymized) which you can find here:
C:\Users\<username>\AppData\Local\io.hoppscotch.desktop\logs\io.hoppscotch.desktop.log~/Library/Logs/io.hoppscotch.desktop/io.hoppscotch.desktop.log~/.local/share/io.hoppscotch.desktop/logs/io.hoppscotch.desktop.log@roopepaajanen commented on GitHub (Nov 25, 2025):
Thanks we'll try out the new release once it is published. I'll create a separate issue if the problem does not disappear.