starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #4949] [bug]: Desktop App login stop working after upgrade #1867

New issue

Closed

opened 2026-03-16 22:10:47 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 22:10:47 +03:00

Owner

Originally created by @John-jk on GitHub (Mar 31, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4949

Originally assigned to: @CuriousCorrelation on GitHub.

Is there an existing issue for this?

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

Current behavior

After updating the client and server to version 2025.3.0, authorization in the desktop app stopped working.
The server response returns an error: 400 Bad Request

Steps to reproduce

In the desktop application, select self hosted server
Click on the Login button
In the window that opens, confirm authorization

Logs and Screenshots

Environment

Production

Hoppscotch Version

Self-hosted

Interceptor

Native - Desktop App

Browsers Affected

No response

Operating System

None

Additional Information

No response

Originally created by @John-jk on GitHub (Mar 31, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4949 Originally assigned to: @CuriousCorrelation on GitHub. ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Current behavior After updating the client and server to version 2025.3.0, authorization in the desktop app stopped working. The server response returns an error: 400 Bad Request ![Image](https://github.com/user-attachments/assets/c5d432d5-03a7-484a-91ce-cd9fc6728f1c) ![Image](https://github.com/user-attachments/assets/b08a7b07-b7cf-423d-b0e7-19097833d42d) ### Steps to reproduce 1. In the desktop application, select self hosted server 2. Click on the Login button 3. In the window that opens, confirm authorization ### Logs and Screenshots ```shell ``` ### Environment Production ### Hoppscotch Version Self-hosted ### Interceptor Native - Desktop App ### Browsers Affected _No response_ ### Operating System None ### Additional Information _No response_

kerem

2026-03-16 22:10:47 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 22:11:03 +03:00

Author

Owner

@LordSimal commented on GitHub (Apr 5, 2025):

I can confirm, that the changes from the linked PR resolve this issue. With these changes, its possible to login to a self-hosted instance via the desktop app again.

@LordSimal commented on GitHub (Apr 5, 2025): I can confirm, that the changes from the linked PR resolve this issue. With these changes, its possible to login to a self-hosted instance via the desktop app again.

kerem commented

2026-03-16 22:11:08 +03:00

Author

Owner

@pankajmyt commented on GitHub (Apr 8, 2025):

any eta on its release?

@pankajmyt commented on GitHub (Apr 8, 2025): any eta on its release?

kerem commented

2026-03-16 22:11:13 +03:00

Author

Owner

@LordSimal commented on GitHub (Apr 8, 2025):

just manually adjust those few lines in the meantime and rebuild.

@LordSimal commented on GitHub (Apr 8, 2025): just manually adjust those few lines in the meantime and rebuild.

kerem commented

2026-03-16 22:11:18 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Apr 11, 2025):

Hello! Closing this issue as resolved - the problem was related to auth requests not specifying headers explicitly, which became necessary after changes to header handling in the platform code. The fix has been implemented in PR #4951 and released in version v2025.3.1.

Important note: Both the desktop app AND your self-hosted instance need to be updated to version v2025.3.1 or newer for the fix to work properly.

For more detailed troubleshooting steps if you're still experiencing issues, please see the discussion in the related issue #4922.

Thanks for reporting and thanks @LordSimal for testing this fix!

@CuriousCorrelation commented on GitHub (Apr 11, 2025): Hello! Closing this issue as resolved - the problem was related to auth requests not specifying headers explicitly, which became necessary after changes to header handling in the platform code. The fix has been implemented in PR #4951 and released in version `v2025.3.1`. Important note: Both the desktop app AND your self-hosted instance need to be updated to version `v2025.3.1` or newer for the fix to work properly. For more detailed troubleshooting steps if you're still experiencing issues, please see the discussion in the related issue #4922. Thanks for reporting and thanks @LordSimal for testing this fix!

kerem referenced this issue

2026-03-17 01:08:23 +03:00

[PR #1867] [MERGED] feat: add socket.io-client version selector menu #3532