starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #4987] [bug]: Issue with google SSO #1894

New issue

Closed

opened 2026-03-16 22:17:42 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 22:17:42 +03:00

Owner

Originally created by @FaranMustafa on GitHub (Apr 12, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4987

Is there an existing issue for this?

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

Current behavior

Description

I have set up Hoppscotch on my own server and integrated both Google and GitHub SSO. However, after signing in using with github works fine but gives status 500 on google

Image:

Expected Behavior

After a successful sign-in with Google or GitHub, I should be redirected to the main interface/dashboard of the app.
Actual Behavior

The app hangs or stays on the same screen post sign-in (as shown in the attached image).
Environment

Self-hosted: Yes

Version: lts

Browser: Firefox 115

OS: linux

SSO Setup: Google & GitHub configured and enabled

Additional Context

If logs are helpful, let me know what to include. Let me know if this could be related to callback URL or some CORS/session issue.

Steps to reproduce

Deploy Hoppscotch on a custom server.

Configure and enable both Google and GitHub SSO.

Attempt to log in using either method.

Observe that after login, the app doesn't redirect or complete the sign-in flow.

Logs and Screenshots

Backend Server | [Nest] 21  - 04/12/2025, 1:07:55 PM   ERROR [ExceptionsHandler] Unauthorized
Backend Server | TokenError: Unauthorized
Backend Server |     at OAuth2Strategy.parseErrorResponse (/dist/backend/node_modules/.pnpm/passport-oauth2@1.8.0/node_modules/passport-oauth2/lib/strategy.js:373:12)
Backend Server |     at OAuth2Strategy._createOAuthError (/dist/backend/node_modules/.pnpm/passport-oauth2@1.8.0/node_modules/passport-oauth2/lib/strategy.js:420:16)
Backend Server |     at /dist/backend/node_modules/.pnpm/passport-oauth2@1.8.0/node_modules/passport-oauth2/lib/strategy.js:177:45
Backend Server |     at /dist/backend/node_modules/.pnpm/oauth@0.10.0/node_modules/oauth/lib/oauth2.js:196:18
Backend Server |     at passBackControl (/dist/backend/node_modules/.pnpm/oauth@0.10.0/node_modules/oauth/lib/oauth2.js:132:9)
Backend Server |     at IncomingMessage.<anonymous> (/dist/backend/node_modules/.pnpm/oauth@0.10.0/node_modules/oauth/lib/oauth2.js:157:7)
Backend Server |     at IncomingMessage.emit (node:events:531:35)
Backend Server |     at endReadableNT (node:internal/streams/readable:1696:12)
Backend Server |     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Environment

Production

Hoppscotch Version

Self-hosted

Interceptor

Not Applicable - Issue not related to network requests

Browsers Affected

No response

Operating System

Linux

Additional Information

No response

Originally created by @FaranMustafa on GitHub (Apr 12, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4987 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Current behavior ### Description I have set up Hoppscotch on my own server and integrated both Google and GitHub SSO. However, after signing in using with github works fine but gives status 500 on google Image: ![Image](https://github.com/user-attachments/assets/39f25eff-ef00-4fff-9cde-b5ff872cca3a) ### Expected Behavior After a successful sign-in with Google or GitHub, I should be redirected to the main interface/dashboard of the app. Actual Behavior The app hangs or stays on the same screen post sign-in (as shown in the attached image). Environment Self-hosted: Yes Version: lts Browser: Firefox 115 OS: linux SSO Setup: Google & GitHub configured and enabled ### Additional Context If logs are helpful, let me know what to include. Let me know if this could be related to callback URL or some CORS/session issue. ### Steps to reproduce Deploy Hoppscotch on a custom server. Configure and enable both Google and GitHub SSO. Attempt to log in using either method. Observe that after login, the app doesn't redirect or complete the sign-in flow. ### Logs and Screenshots ```shell Backend Server | [Nest] 21 - 04/12/2025, 1:07:55 PM ERROR [ExceptionsHandler] Unauthorized Backend Server | TokenError: Unauthorized Backend Server | at OAuth2Strategy.parseErrorResponse (/dist/backend/node_modules/.pnpm/passport-oauth2@1.8.0/node_modules/passport-oauth2/lib/strategy.js:373:12) Backend Server | at OAuth2Strategy._createOAuthError (/dist/backend/node_modules/.pnpm/passport-oauth2@1.8.0/node_modules/passport-oauth2/lib/strategy.js:420:16) Backend Server | at /dist/backend/node_modules/.pnpm/passport-oauth2@1.8.0/node_modules/passport-oauth2/lib/strategy.js:177:45 Backend Server | at /dist/backend/node_modules/.pnpm/oauth@0.10.0/node_modules/oauth/lib/oauth2.js:196:18 Backend Server | at passBackControl (/dist/backend/node_modules/.pnpm/oauth@0.10.0/node_modules/oauth/lib/oauth2.js:132:9) Backend Server | at IncomingMessage.<anonymous> (/dist/backend/node_modules/.pnpm/oauth@0.10.0/node_modules/oauth/lib/oauth2.js:157:7) Backend Server | at IncomingMessage.emit (node:events:531:35) Backend Server | at endReadableNT (node:internal/streams/readable:1696:12) Backend Server | at process.processTicksAndRejections (node:internal/process/task_queues:82:21) ``` ### Environment Production ### Hoppscotch Version Self-hosted ### Interceptor Not Applicable - Issue not related to network requests ### Browsers Affected _No response_ ### Operating System Linux ### Additional Information _No response_

kerem

2026-03-16 22:17:42 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 22:17:58 +03:00

Author

Owner

@FaranMustafa commented on GitHub (Apr 18, 2025):

Closing the issue solved it! there was issue with client secret but still would suggest instead of Unauthorised token should've been raised by appropriate error.

@FaranMustafa commented on GitHub (Apr 18, 2025): Closing the issue solved it! there was issue with client secret but still would suggest instead of Unauthorised token should've been raised by appropriate error.

kerem referenced this issue

2026-03-17 01:09:29 +03:00

[PR #1894] [CLOSED] Save example for request #3552