starred/hoppscotch

Fork 0

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

[GH-ISSUE #4735] [bug]: Failed to obtain access token via MicrosoftSSO behind a proxy #1769

New issue

Open

opened 2026-03-16 21:40:37 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 21:40:37 +03:00

Owner

Originally created by @MassBklf on GitHub (Feb 7, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4735

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I try a login via Microsoft SSO, I get a 500 server error.

Browserlog:

statusCode | 500
message | "Internal server error"

Serverlog:

hoppscotch-aio       | Backend Server | [Nest] 37  - 02/07/2025, 10:06:39 AM   ERROR [ExceptionsHandler] Failed to obtain access token
hoppscotch-aio       | Backend Server | InternalOAuthError: Failed to obtain access token
hoppscotch-aio       | Backend Server |     at OAuth2Strategy._createOAuthError (/dist/backend/node_modules/.pnpm/passport-oauth2@1.8.0/node_modules/passport-oauth2/lib/strategy.js:423:17)
hoppscotch-aio       | Backend Server |     at /dist/backend/node_modules/.pnpm/passport-oauth2@1.8.0/node_modules/passport-oauth2/lib/strategy.js:177:45
hoppscotch-aio       | Backend Server |     at /dist/backend/node_modules/.pnpm/oauth@0.10.0/node_modules/oauth/lib/oauth2.js:196:18
hoppscotch-aio       | Backend Server |     at ClientRequest.<anonymous> (/dist/backend/node_modules/.pnpm/oauth@0.10.0/node_modules/oauth/lib/oauth2.js:166:7)
hoppscotch-aio       | Backend Server |     at ClientRequest.emit (node:events:519:28)
hoppscotch-aio       | Backend Server |     at TLSSocket.socketErrorListener (node:_http_client:500:9)
hoppscotch-aio       | Backend Server |     at TLSSocket.emit (node:events:519:28)
hoppscotch-aio       | Backend Server |     at emitErrorNT (node:internal/streams/destroy:169:8)
hoppscotch-aio       | Backend Server |     at emitErrorCloseNT (node:internal/streams/destroy:128:3)
hoppscotch-aio       | Backend Server |     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

The server is behind a proxy and the problem is that the backend directly request the Microsoft Auth Servers, which is not possible.

Steps to reproduce

!! All behind a Proxy !!

Setup .env with microsoft auth
Host the newest Hoppscotch AIO Version 2025.1.0 on Docker
Try to login

Environment

Production

Version

Self-hosted

Originally created by @MassBklf on GitHub (Feb 7, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4735 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Current behavior When I try a login via Microsoft SSO, I get a 500 server error. Browserlog: ``` statusCode | 500 message | "Internal server error" ``` Serverlog: ``` hoppscotch-aio | Backend Server | [Nest] 37 - 02/07/2025, 10:06:39 AM ERROR [ExceptionsHandler] Failed to obtain access token hoppscotch-aio | Backend Server | InternalOAuthError: Failed to obtain access token hoppscotch-aio | Backend Server | at OAuth2Strategy._createOAuthError (/dist/backend/node_modules/.pnpm/passport-oauth2@1.8.0/node_modules/passport-oauth2/lib/strategy.js:423:17) hoppscotch-aio | Backend Server | at /dist/backend/node_modules/.pnpm/passport-oauth2@1.8.0/node_modules/passport-oauth2/lib/strategy.js:177:45 hoppscotch-aio | Backend Server | at /dist/backend/node_modules/.pnpm/oauth@0.10.0/node_modules/oauth/lib/oauth2.js:196:18 hoppscotch-aio | Backend Server | at ClientRequest.<anonymous> (/dist/backend/node_modules/.pnpm/oauth@0.10.0/node_modules/oauth/lib/oauth2.js:166:7) hoppscotch-aio | Backend Server | at ClientRequest.emit (node:events:519:28) hoppscotch-aio | Backend Server | at TLSSocket.socketErrorListener (node:_http_client:500:9) hoppscotch-aio | Backend Server | at TLSSocket.emit (node:events:519:28) hoppscotch-aio | Backend Server | at emitErrorNT (node:internal/streams/destroy:169:8) hoppscotch-aio | Backend Server | at emitErrorCloseNT (node:internal/streams/destroy:128:3) hoppscotch-aio | Backend Server | at process.processTicksAndRejections (node:internal/process/task_queues:82:21) ``` The server is behind a proxy and the problem is that the backend directly request the Microsoft Auth Servers, which is not possible. ### Steps to reproduce !! All behind a Proxy !! 1. Setup .env with microsoft auth 2. Host the newest Hoppscotch AIO Version 2025.1.0 on Docker 3. Try to login ### Environment Production ### Version Self-hosted

kerem added the

bug

need testing

labels

2026-03-16 21:40:37 +03:00

kerem commented

2026-03-16 21:40:49 +03:00

Author

Owner

@ericciccone commented on GitHub (Mar 31, 2025):

can you post your microsoft.strategy.js

@ericciccone commented on GitHub (Mar 31, 2025): can you post your microsoft.strategy.js

kerem commented

2026-03-16 21:40:54 +03:00

Author

Owner

@MatthiasSalonkee commented on GitHub (Oct 31, 2025):

Hi,
I'm having the same issue but with github auth
The authentication works well, the user is connected, but the callback requests fails with 500 :

Backend Server \| ::ffff:127.0.0.1 GET /v1/auth/github/callback?code=xxx&state=xxx 500 - 170.928 ms 
Backend Server \| [31m[Nest] 69 - [39m10/31/2025, 8:14:34 AM [31m ERROR[39m [38;5;3m[ExceptionsHandler] [39mError: Failed to obtain access token
Backend Server \| at [90m/dist/backend/[39mnode_modules/[4m.pnpm[24m/passport-oauth2@1.8.0/node_modules/[4mpassport-oauth2[24m/lib/strategy.js:178:49
Backend Server \| at [90m/dist/backend/[39mnode_modules/[4m.pnpm[24m/oauth@0.10.0/node_modules/[4moauth[24m/lib/oauth2.js:214:7
Backend Server \| at passBackControl [90m(/dist/backend/[39mnode_modules/[4m.pnpm[24m/oauth@0.10.0/node_modules/[4moauth[24m/lib/oauth2.js:134:9[90m)[39m
Backend Server \| at IncomingMessage.<anonymous> [90m(/dist/backend/[39mnode_modules/[4m.pnpm[24m/oauth@0.10.0/node_modules/[4moauth[24m/lib/oauth2.js:157:7[90m)[39m
Backend Server \| [90m at IncomingMessage.emit (node:events:530:35)[39m
Backend Server \| [90m at endReadableNT (node:internal/streams/readable:1698:12)[39m
Backend Server \| [90m at process.processTicksAndRejections (node:internal/process/task_queues:90:21)[39m

Did anyone found the root cause and a fix ?

@MatthiasSalonkee commented on GitHub (Oct 31, 2025): Hi, I'm having the same issue but with github auth The authentication works well, the user is connected, but the callback requests fails with 500 : ``` Backend Server \| ::ffff:127.0.0.1 GET /v1/auth/github/callback?code=xxx&state=xxx 500 - 170.928 ms Backend Server \| [31m[Nest] 69 - [39m10/31/2025, 8:14:34 AM [31m ERROR[39m [38;5;3m[ExceptionsHandler] [39mError: Failed to obtain access token Backend Server \| at [90m/dist/backend/[39mnode_modules/[4m.pnpm[24m/passport-oauth2@1.8.0/node_modules/[4mpassport-oauth2[24m/lib/strategy.js:178:49 Backend Server \| at [90m/dist/backend/[39mnode_modules/[4m.pnpm[24m/oauth@0.10.0/node_modules/[4moauth[24m/lib/oauth2.js:214:7 Backend Server \| at passBackControl [90m(/dist/backend/[39mnode_modules/[4m.pnpm[24m/oauth@0.10.0/node_modules/[4moauth[24m/lib/oauth2.js:134:9[90m)[39m Backend Server \| at IncomingMessage.<anonymous> [90m(/dist/backend/[39mnode_modules/[4m.pnpm[24m/oauth@0.10.0/node_modules/[4moauth[24m/lib/oauth2.js:157:7[90m)[39m Backend Server \| [90m at IncomingMessage.emit (node:events:530:35)[39m Backend Server \| [90m at endReadableNT (node:internal/streams/readable:1698:12)[39m Backend Server \| [90m at process.processTicksAndRejections (node:internal/process/task_queues:90:21)[39m ``` Did anyone found the root cause and a fix ?

kerem commented

2026-03-16 21:40:59 +03:00

Author

Owner

@EmperorArthur commented on GitHub (Nov 19, 2025):

@MassBklf This may be related to #5598, with the proxy failure masking the 400 error being returned by Azure.

@EmperorArthur commented on GitHub (Nov 19, 2025): @MassBklf This may be related to #5598, with the proxy failure masking the 400 error being returned by Azure.

kerem referenced this issue

2026-03-17 01:05:37 +03:00

[PR #1769] [MERGED] fix: broken settings persistence on the home page #3484