mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5387] [bug]: Enterprise Edition (self-hosted) :3170/v1/onboarding/config API not retrieving values from the .env file #2066
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#2066
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 @klewitzke on GitHub (Sep 17, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5387
Originally assigned to: @mirarifhasan on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Edge
Operating System
Windows
Bug Description
We deployed Enterprise Edition using docker-compose.yml file below:
We are able to access the frontend portal and admin portal over ports 3000 and 3100 respectively (see attached screenshots).
After clicking "Start Onboarding" and then going to configure the SMTP settings, upon entering the settings and clicking "Save Auth Config" button we immediately receive the HTTP 400 Bad Request error in the console as shown below.
Pointing the browser to :3170/v1/onboarding/config returns the JSON response below (all values null), although these values are configured in the .env file.
{"VITE_ALLOWED_AUTH_PROVIDERS":null,"GOOGLE_CLIENT_ID":null,"GOOGLE_CLIENT_SECRET":null,"GOOGLE_CALLBACK_URL":null,"GOOGLE_SCOPE":null,"GITHUB_CLIENT_ID":null,"GITHUB_CLIENT_SECRET":null,"GITHUB_CALLBACK_URL":null,"GITHUB_SCOPE":null,"GITHUB_AUTHORIZATION_URL":null,"GITHUB_TOKEN_URL":null,"GITHUB_USER_PROFILE_URL":null,"GITHUB_USER_EMAIL_URL":null,"IS_GITHUB_ENTERPRISE_ENABLED":null,"MICROSOFT_CLIENT_ID":null,"MICROSOFT_CLIENT_SECRET":null,"MICROSOFT_CALLBACK_URL":null,"MICROSOFT_SCOPE":null,"MICROSOFT_TENANT":null,"MAILER_SMTP_ENABLE":null,"MAILER_USE_CUSTOM_CONFIGS":null,"MAILER_ADDRESS_FROM":null,"MAILER_SMTP_URL":null,"MAILER_SMTP_HOST":null,"MAILER_SMTP_PORT":null,"MAILER_SMTP_SECURE":null,"MAILER_SMTP_USER":null,"MAILER_SMTP_PASSWORD":null,"MAILER_TLS_REJECT_UNAUTHORIZED":null,"SAML_ISSUER":null,"SAML_AUDIENCE":null,"SAML_CALLBACK_URL":null,"SAML_CERT":null,"SAML_ENTRY_POINT":null,"SAML_WANT_ASSERTIONS_SIGNED":null,"SAML_WANT_RESPONSE_SIGNED":null,"OIDC_PROVIDER_NAME":null,"OIDC_ISSUER":null,"OIDC_AUTH_URL":null,"OIDC_TOKEN_URL":null,"OIDC_USER_INFO_URL":null,"OIDC_CLIENT_ID":null,"OIDC_CLIENT_SECRET":null,"OIDC_CALLBACK_URL":null,"OIDC_SCOPE":null}Below is our .env file:
Deployment Type
Self-hosted (on-prem deployment)
Version
2025.8.1
@mirarifhasan commented on GitHub (Sep 17, 2025):
Hello @klewitzke,
We only load a limited set of environment variables from the
.envfile to keep the configuration clean (see referance)Because of this, SMTP settings need to be configured through the Admin dashboard during the onboarding process.
Since you’re encountering a
400 Bad RequestonPOST /onboarding/config, could you please share the backend container error logs generated when making that API call? This will help us better understand the issue.@klewitzke commented on GitHub (Sep 17, 2025):
@mirarifhasan Yes, can you please let me know how/where the backend container error logs are stored?
@mirarifhasan commented on GitHub (Sep 17, 2025):
You can find the logs inside the Docker container by running the following command:
docker logs <backend_container_id>@klewitzke commented on GitHub (Sep 17, 2025):
@mirarifhasan please find the complete log here: hoppscotch_backend_logs_250917_0844.txt
Each time the "Save Auth Config" button is clicked, the following entry is added to the log:
@mirarifhasan commented on GitHub (Sep 17, 2025):
Thanks for sharing the logs, @klewitzke 🙏
On the backend, we validate the SMTP URL that gets entered. Could you share the SMTP URL you’re using? That will help us adjust the validation logic for our upcoming release.
In the meantime, since you already have the custom values, you can also try configuring them directly with the following:
@klewitzke commented on GitHub (Sep 17, 2025):
@mirarifhasan good to know, thank you! Sure, the SMTP URL is in the format: http://mail-xx.xxx.state.xx.us (It's an internal URL so I appreciate your understanding in not posting it completely, but each letter has been swapped out with an 'x'.)
I did attempt using the values as shown below, but the issue is still occurring.
@klewitzke commented on GitHub (Sep 17, 2025):
@mirarifhasan - I have no idea what happened, but it is working now! I did select "Use Custom Configs" I will close this Issue. Thank you for your help.