[GH-ISSUE #3901] [Feature Request] support dashboard url prefix config #3092

Closed
opened 2026-05-05 14:00:09 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @kangqf on GitHub (Dec 28, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3901

Describe the feature request

When we want to use some subpath to access dashboard, for example https://a.b.com/admin, we need rewrite /api and /statics in nginx.conf to remove admin prefix. But It may occurs conflict in some condition when some other service use the same prefix api or statics, so we need support dashboard url prefix in config file like webServer.assetsDir

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @kangqf on GitHub (Dec 28, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3901 ### Describe the feature request When we want to use some subpath to access dashboard, for example https://a.b.com/admin, we need rewrite /api and /statics in nginx.conf to remove admin prefix. But It may occurs conflict in some condition when some other service use the same prefix api or statics, so we need support dashboard url prefix in config file like `webServer.assetsDir` ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others
gitea-mirror 2026-05-05 14:00:09 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 25, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:1909292017 --> @github-actions[bot] commented on GitHub (Jan 25, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3092
No description provided.