mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4696] [bug]: Admin panel requests authentication setup despite being configured in .env #1750
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#1750
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 @Palaos1510 on GitHub (Jan 24, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4696
Is there an existing issue for this?
Current behavior
We are running Hoppscotch using docker-compose, and the .env file is correctly configured, including authentication keys. However, when accessing the admin panel, it asks us to set up an authentication method to proceed.
🔍 Expected Behavior
Since we have already defined VITE_ALLOWED_AUTH_PROVIDERS=EMAIL,GOOGLE in our .env, the admin panel should recognize the configured authentication methods and allow access without requiring additional setup.
✅ Current Behavior
🛠 Current Configuration
Our .env file contains:
`
`
Our docker-compose.yml configuration:
`
`
and this is my nginx.conf: for the site
`
`
🛑 Debugging Logs
Hoppscotch Admin Logs (docker compose logs hoppscotch-admin)
`
`
Hoppscotch Backend Logs (docker compose logs hoppscotch-backend)
`
`
❓ Questions
Steps to reproduce
Deploy Hoppscotch Community Edition using docker-compose, ensuring that the .env file is properly configured with authentication settings (VITE_ALLOWED_AUTH_PROVIDERS=EMAIL,GOOGLE).
Follow the official recommendation to host the admin panel on a separate URL (e.g., VITE_ADMIN_URL=https://admin.hupp.example.com).
Start the services using:
Access the frontend (https://hupp.example.com) and verify that it loads without issues.
Try accessing the admin panel (https://admin.hupp.example.com).
Observe that the admin panel asks to set up an authentication method, even though authentication is already configured in .env.
Environment
Production
Version
Cloud
@jianzhichu commented on GitHub (Mar 4, 2025):
I'm in the same situation as you, have you solved it yet
@floviolleau commented on GitHub (Oct 1, 2025):
Hi,
I have the same issue today. Here is my docker-compose.yml file:
If I do
docker exec -it hoppscotch-aio bashand inside the container I doenvI see all variables from .envAny clues?
Thanks
@mirarifhasan commented on GitHub (Oct 6, 2025):
@Palaos1510
I noticed a couple of configuration issues in your setup:
It appears the frontend URL is being used instead of the backend base URL.
I'd recommend trying our latest version of Hoppscotch, which features a more streamlined .env configuration with fewer variables for easier setup.
@jianzhichu @floviolleau
Could you please provide additional details about your setup? Specifically:
This will help us better understand and resolve the problem. Thank you!
@mirarifhasan commented on GitHub (Oct 15, 2025):
Closing this issue due to inactivity. Please feel free to reopen it if the problem persists or you need further assistance.