starred/hoppscotch

Fork 0

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

[GH-ISSUE #5238] [bug]: Unable to load auth providers when deploying on cloud #1999

New issue

Closed

opened 2026-03-16 22:48:35 +03:00 by kerem · 5 comments

kerem commented

2026-03-16 22:48:35 +03:00

Owner

Originally created by @Shivangi0503 on GitHub (Jul 11, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5238

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

Linux

Bug Description

still facing this issue as we cannot use port 80 with AWS, 3000 works but gives the "unable to load auth providers" error. Any solution?

Deployment Type

Self-hosted (on-prem deployment)

Version

No response

Originally created by @Shivangi0503 on GitHub (Jul 11, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5238 <img width="735" height="1355" alt="Image" src="https://github.com/user-attachments/assets/ea51d4a7-2f8f-4324-859e-955372aa1a02" /> ### 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 Linux ### Bug Description still facing this issue as we cannot use port 80 with AWS, 3000 works but gives the "unable to load auth providers" error. Any solution? ### Deployment Type Self-hosted (on-prem deployment) ### Version _No response_

kerem

2026-03-16 22:48:35 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 22:48:51 +03:00

Author

Owner

@mirarifhasan commented on GitHub (Jul 11, 2025):

Hi @Shivangi0503,
Thanks for reporting the issue!

Could you please let us know which AWS service you're using (e.g., EC2)?
If you're running the Hoppscotch application using Docker, could you also share the output of docker ps?

Additionally, please share the values you've set in your .env file for the following keys (you can redact any sensitive info like domain names if you prefer):

WHITELISTED_ORIGINS  
ENABLE_SUBPATH_BASED_ACCESS  
VITE_BASE_URL  
VITE_SHORTCODE_BASE_URL  
VITE_ADMIN_URL  
VITE_BACKEND_GQL_URL  
VITE_BACKEND_WS_URL  
VITE_BACKEND_API_URL

@mirarifhasan commented on GitHub (Jul 11, 2025): Hi @Shivangi0503, Thanks for reporting the issue! Could you please let us know which AWS service you're using (e.g., EC2)? If you're running the Hoppscotch application using Docker, could you also share the output of `docker ps`? Additionally, please share the values you've set in your `.env` file for the following keys (you can redact any sensitive info like domain names if you prefer): ``` WHITELISTED_ORIGINS ENABLE_SUBPATH_BASED_ACCESS VITE_BASE_URL VITE_SHORTCODE_BASE_URL VITE_ADMIN_URL VITE_BACKEND_GQL_URL VITE_BACKEND_WS_URL VITE_BACKEND_API_URL ```

kerem commented

2026-03-16 22:48:56 +03:00

Author

Owner

@faritor commented on GitHub (Jul 20, 2025):

Hi @mirarifhasan ,

I also encountered this problem. I deployed it in the local area network using docker compose.

use image: hoppscotch/hoppscotch

I deployed aio to the machine with 192.168.1.7 and made adjustments to prevent port conflicts

docker-compose.yaml

services:
  hoppscotch:
    image: hoppscotch/hoppscotch
    container_name: hoppscotch
    env_file:
      - ./config/.env
    restart: always
    ports:
      - "56430:3000"
      - "56431:3100"
      - "56437:3170"

.env

DATABASE_URL=postgresql://root:root@192.168.1.9:5432/hoppscotch

JWT_SECRET="a9101da6bcabf"
TOKEN_SALT_COMPLEXITY=10
MAGIC_LINK_TOKEN_VALIDITY=3
REFRESH_TOKEN_VALIDITY=604800000
ACCESS_TOKEN_VALIDITY=86400000
SESSION_SECRET="569c2f60381"
ALLOW_SECURE_COOKIES=false

DATA_ENCRYPTION_KEY="98c8d7ae***864c"

REDIRECT_URL="http://192.168.1.7:56430"
WHITELISTED_ORIGINS="http://localhost:3170,http://localhost:3000,http://localhost:3100,app://localhost_3200,app://hoppscotch,http://192.168.1.7:56437,http://192.168.1.7:56430,http://192.168.1.7:56431,app://"
VITE_ALLOWED_AUTH_PROVIDERS=EMAIL

MAILER_SMTP_ENABLE="true"
MAILER_USE_CUSTOM_CONFIGS="true"
MAILER_ADDRESS_FROM="notify@ikebot.com"


MAILER_SMTP_HOST="smtp.demo.com"
MAILER_SMTP_PORT="465"
MAILER_SMTP_SECURE="true"
MAILER_SMTP_USER="no-reply@demo.com"
MAILER_SMTP_PASSWORD="******"
MAILER_TLS_REJECT_UNAUTHORIZED="false"

RATE_LIMIT_TTL=60
RATE_LIMIT_MAX=100

VITE_BASE_URL=http://192.168.1.7:56430
VITE_SHORTCODE_BASE_URL=http://192.168.1.7:56430
VITE_ADMIN_URL=http://192.168.1.7:56431

VITE_BACKEND_GQL_URL=http://localhost:3170/graphql
VITE_BACKEND_WS_URL=ws://localhost:3170/graphql
VITE_BACKEND_API_URL=http://localhost:3170/v1

VITE_APP_TOS_LINK=https://docs.hoppscotch.io/support/terms
VITE_APP_PRIVACY_POLICY_LINK=https://docs.hoppscotch.io/support/privacy

VITE_PROXYSCOTCH_ACCESS_TOKEN=

ENABLE_SUBPATH_BASED_ACCESS=false

I still have one more question. When I set the allow to *, I still can't use the mac version of the desktop application to add instances, and it always prompts the following sentence

WHITELISTED_ORIGINS="*"

Verification error: Key validation failed: HTTP request failed: error decoding response body

looking forward to solving these problems

@faritor commented on GitHub (Jul 20, 2025): Hi @mirarifhasan , I also encountered this problem. I deployed it in the local area network using docker compose. use image: hoppscotch/hoppscotch I deployed aio to the machine with 192.168.1.7 and made adjustments to prevent port conflicts docker-compose.yaml ``` services: hoppscotch: image: hoppscotch/hoppscotch container_name: hoppscotch env_file: - ./config/.env restart: always ports: - "56430:3000" - "56431:3100" - "56437:3170" ``` .env ``` DATABASE_URL=postgresql://root:root@192.168.1.9:5432/hoppscotch JWT_SECRET="a9101da6bcabf" TOKEN_SALT_COMPLEXITY=10 MAGIC_LINK_TOKEN_VALIDITY=3 REFRESH_TOKEN_VALIDITY=604800000 ACCESS_TOKEN_VALIDITY=86400000 SESSION_SECRET="569c2f60381" ALLOW_SECURE_COOKIES=false DATA_ENCRYPTION_KEY="98c8d7ae***864c" REDIRECT_URL="http://192.168.1.7:56430" WHITELISTED_ORIGINS="http://localhost:3170,http://localhost:3000,http://localhost:3100,app://localhost_3200,app://hoppscotch,http://192.168.1.7:56437,http://192.168.1.7:56430,http://192.168.1.7:56431,app://" VITE_ALLOWED_AUTH_PROVIDERS=EMAIL MAILER_SMTP_ENABLE="true" MAILER_USE_CUSTOM_CONFIGS="true" MAILER_ADDRESS_FROM="notify@ikebot.com" MAILER_SMTP_HOST="smtp.demo.com" MAILER_SMTP_PORT="465" MAILER_SMTP_SECURE="true" MAILER_SMTP_USER="no-reply@demo.com" MAILER_SMTP_PASSWORD="******" MAILER_TLS_REJECT_UNAUTHORIZED="false" RATE_LIMIT_TTL=60 RATE_LIMIT_MAX=100 VITE_BASE_URL=http://192.168.1.7:56430 VITE_SHORTCODE_BASE_URL=http://192.168.1.7:56430 VITE_ADMIN_URL=http://192.168.1.7:56431 VITE_BACKEND_GQL_URL=http://localhost:3170/graphql VITE_BACKEND_WS_URL=ws://localhost:3170/graphql VITE_BACKEND_API_URL=http://localhost:3170/v1 VITE_APP_TOS_LINK=https://docs.hoppscotch.io/support/terms VITE_APP_PRIVACY_POLICY_LINK=https://docs.hoppscotch.io/support/privacy VITE_PROXYSCOTCH_ACCESS_TOKEN= ENABLE_SUBPATH_BASED_ACCESS=false ``` I still have one more question. When I set the allow to *, I still can't use the mac version of the desktop application to add instances, and it always prompts the following sentence ``` WHITELISTED_ORIGINS="*" ``` `Verification error: Key validation failed: HTTP request failed: error decoding response body ` looking forward to solving these problems

kerem commented

2026-03-16 22:49:01 +03:00

Author

Owner

@mirarifhasan commented on GitHub (Jul 21, 2025):

Hi @faritor

Please update the host and port in the following environment variables:

VITE_BACKEND_GQL_URL=http://localhost:3170/graphql
VITE_BACKEND_WS_URL=ws://localhost:3170/graphql
VITE_BACKEND_API_URL=http://localhost:3170/v1

Also, to access the desktop app, make sure to expose port 3200 (with proper WHITELISTED_ORIGINS or "*" for the time being) in your docker-compose file.
Let me know if this resolves both the browser and desktop issues.

@mirarifhasan commented on GitHub (Jul 21, 2025): Hi @faritor Please update the host and port in the following environment variables: ``` VITE_BACKEND_GQL_URL=http://localhost:3170/graphql VITE_BACKEND_WS_URL=ws://localhost:3170/graphql VITE_BACKEND_API_URL=http://localhost:3170/v1 ``` Also, to access the desktop app, make sure to expose port **3200** (with proper WHITELISTED_ORIGINS or "*" for the time being) in your docker-compose file. Let me know if this resolves both the browser and desktop issues.

kerem commented

2026-03-16 22:49:06 +03:00

Author

Owner

@faritor commented on GitHub (Jul 21, 2025):

thank you for your reply. @mirarifhasan ,

you've solved a big problem for me! I can now log in via email, and the mac app has also been successfully connected.

however, here I have a suggestion. In the official documentation, I don't seem to see any mention that the app connection uses port 3200. Moreover, after I successfully connect, I hope to be able to modify the instance name. Currently, I am using the ip connection [192.168.1.7], and the instance name displayed is [1.7], which is not very aesthetically pleasing I want to customize this name

@faritor commented on GitHub (Jul 21, 2025): thank you for your reply. @mirarifhasan , you've solved a big problem for me! I can now log in via email, and the mac app has also been successfully connected. however, here I have a suggestion. In the official documentation, I don't seem to see any mention that the app connection uses port 3200. Moreover, after I successfully connect, I hope to be able to modify the instance name. Currently, I am using the ip connection [192.168.1.7], and the instance name displayed is [1.7], which is not very aesthetically pleasing I want to customize this name

kerem commented

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

Author

Owner

@mirarifhasan commented on GitHub (Jul 21, 2025):

Renaming is not supported in this version. Noted your request, will forward to the team.

@mirarifhasan commented on GitHub (Jul 21, 2025): Renaming is not supported in this version. Noted your request, will forward to the team.

kerem referenced this issue

2026-03-17 01:11:56 +03:00

[PR #1999] [MERGED] feat: socketio bearer authentication #3596