github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-22 09:32:36 -05:00
Code Issues 959 Packages Projects Releases 74 Wiki Activity

[GH-ISSUE #1422] Initial setup fails with 404 - Web UI sends API requests to wrong port #1901

New Issue
Closed
opened 2026-04-16 08:45:38 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-16 08:45:38 -05:00
Owner
Copy Link

Originally created by @stlas on GitHub (Sep 5, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1422

Bug Description

When attempting to create the initial server admin account through the Web UI, the request fails with a 404 error. The Web UI incorrectly sends API requests to port 8080 (Web UI port) instead of port 3000 (API port).

Steps to Reproduce

  1. Fresh installation of Pangolin (tested with v1.8.0 and latest)
  2. Start container with standard port mapping:
    • 3000:3000 (API)
    • 8080:3002 (Web UI)
  3. Navigate to http://server:8080
  4. Fill in initial setup form with email, password, and setup token
  5. Click "Create Admin Account"
  6. Observe 404 error

Expected Behavior

API request should go to http://server:3000/api/v1/auth/set-server-admin

Actual Behavior

API request goes to http://server:8080/api/v1/auth/set-server-admin (wrong port)

Environment

  • Pangolin Version: 1.8.0, 1.9.3, latest
  • Deployment: Docker (fosrl/pangolin)
  • OS: Debian 12
  • Browser: Chrome/Firefox (all affected)

Additional Context

  • Setup token is correctly generated in logs: Token: xmxfh6yjpyd95zx9so0qh3ed6y39tbam
  • Database shows token exists and is unused
  • Direct API calls to port 3000 fail with "CSRF token missing or invalid"
  • Network tab shows: PUT http://server:8080/api/v1/auth/set-server-admin 404 (Not Found)

Workaround Attempts

  1. ✗ Nginx reverse proxy - Still hits wrong port
  2. ✗ Direct API calls - Blocked by CSRF protection
  3. ✗ Different versions - All affected

Suggested Fix

The Next.js frontend should be configured to send API requests to the correct port (3000) or use relative URLs that get properly proxied.

Config Used

app:
  dashboard_url: "http://XXX.XXX.XXX.XXX:8080"
  log_level: "info"

server:
  external_port: 3000
  internal_port: 3001
  next_port: 3002
  secret: "secret-key-here"

domains:
  example:
    base_domain: "example.com"
    cert_resolver: "self-signed"

This makes initial setup impossible without modifying the deployment or using workarounds.

Originally created by @stlas on GitHub (Sep 5, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1422 ### Bug Description When attempting to create the initial server admin account through the Web UI, the request fails with a 404 error. The Web UI incorrectly sends API requests to port 8080 (Web UI port) instead of port 3000 (API port). ### Steps to Reproduce 1. Fresh installation of Pangolin (tested with v1.8.0 and latest) 2. Start container with standard port mapping: - 3000:3000 (API) - 8080:3002 (Web UI) 3. Navigate to `http://server:8080` 4. Fill in initial setup form with email, password, and setup token 5. Click "Create Admin Account" 6. Observe 404 error ### Expected Behavior API request should go to `http://server:3000/api/v1/auth/set-server-admin` ### Actual Behavior API request goes to `http://server:8080/api/v1/auth/set-server-admin` (wrong port) ### Environment - **Pangolin Version:** 1.8.0, 1.9.3, latest - **Deployment:** Docker (fosrl/pangolin) - **OS:** Debian 12 - **Browser:** Chrome/Firefox (all affected) ### Additional Context - Setup token is correctly generated in logs: `Token: xmxfh6yjpyd95zx9so0qh3ed6y39tbam` - Database shows token exists and is unused - Direct API calls to port 3000 fail with "CSRF token missing or invalid" - Network tab shows: `PUT http://server:8080/api/v1/auth/set-server-admin 404 (Not Found)` ### Workaround Attempts 1. ✗ Nginx reverse proxy - Still hits wrong port 2. ✗ Direct API calls - Blocked by CSRF protection 3. ✗ Different versions - All affected ### Suggested Fix The Next.js frontend should be configured to send API requests to the correct port (3000) or use relative URLs that get properly proxied. ### Config Used ```yaml app: dashboard_url: "http://XXX.XXX.XXX.XXX:8080" log_level: "info" server: external_port: 3000 internal_port: 3001 next_port: 3002 secret: "secret-key-here" domains: example: base_domain: "example.com" cert_resolver: "self-signed" ``` This makes initial setup impossible without modifying the deployment or using workarounds.
GiteaMirror added the stale label 2026-04-16 08:45:38 -05:00
GiteaMirror commented 2026-04-16 08:45:41 -05:00
Author
Owner
Copy Link

@Pallavikumarimdb commented on GitHub (Sep 6, 2025):

The issue most likely coming from how the UI choosing the API URL. Right now it compares the browser port with server.nextPort (3002), but in your setup the browser only sees 8080 from the mapping 8080:3002. Since those don’t match, the UI falls back to http://server:8080/api/..., which explains the 404.

As a temporary workaround you can try exposing the UI on the same port inside and outside the container (3002:3002).

This looks like a bug in the client logic for mapped ports @oschwartz10612 .

<!-- gh-comment-id:3261667315 --> @Pallavikumarimdb commented on GitHub (Sep 6, 2025): The issue most likely coming from how the UI choosing the API URL. Right now it compares the browser port with server.nextPort (3002), but in your setup the browser only sees 8080 from the mapping 8080:3002. Since those don’t match, the UI falls back to http://server:8080/api/..., which explains the 404. As a temporary workaround you can try exposing the UI on the same port inside and outside the container (3002:3002). This looks like a bug in the client logic for mapped ports @oschwartz10612 .
GiteaMirror commented 2026-04-16 08:45:41 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 21, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:3315392280 --> @github-actions[bot] commented on GitHub (Sep 21, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
GiteaMirror commented 2026-04-16 08:45:42 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 5, 2025):

This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.

<!-- gh-comment-id:3368628932 --> @github-actions[bot] commented on GitHub (Oct 5, 2025): This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#1901
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?