[GH-ISSUE #3829] Server Dashboard behind a Web Proxy

gitea-mirror commented

2026-05-05 13:58:09 -06:00

Owner

Originally created by @ArminRadmueller on GitHub (Dec 6, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3829

Describe the feature request

I would like to make the server dashboard easier accessible to my users and publish it behind a reverse proxy. Unfortunately, an HTTP/301 rewirte / causes the page not to work.

example config in Apache:

<VirtualHost *:443>
  ServerName admin.mycompany.com

  RewriteEngine On

  <Location />
    Require all granted
  </Location>

  # if reports is requested go to it as it is and skip following rules
  RewriteRule "^/connect.*" - [NC,L]

  <Location /connect >
    ProxyPass         http://192.168.1.1:7500/
    ProxyPassReverse  http://192.168.1.1:7500/
  </Location>

</VirtualHost>

Describe alternatives you've considered

Is it possible to introduce a URI variable?
in this case e.g. https://admin.mycompany.com/connect

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @ArminRadmueller on GitHub (Dec 6, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3829 ### Describe the feature request I would like to make the server dashboard easier accessible to my users and publish it behind a reverse proxy. Unfortunately, an HTTP/301 rewirte / causes the page not to work. example config in Apache: ``` <VirtualHost *:443> ServerName admin.mycompany.com RewriteEngine On <Location /> Require all granted </Location> # if reports is requested go to it as it is and skip following rules RewriteRule "^/connect.*" - [NC,L] <Location /connect > ProxyPass http://192.168.1.1:7500/ ProxyPassReverse http://192.168.1.1:7500/ </Location> </VirtualHost> ``` ### Describe alternatives you've considered Is it possible to introduce a URI variable? in this case e.g. https://admin.mycompany.com/connect ### Affected area - [ ] Docs - [X] Installation - [ ] Performance and Scalability - [X] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:58:09 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:58:12 -06:00

Author

Owner

@fatedier commented on GitHub (Dec 7, 2023):

I don't understand Apache configuration very well, but if it's a 301 issue, I think you can directly implement this URL rewrite in the Apache configuration.

@fatedier commented on GitHub (Dec 7, 2023): I don't understand Apache configuration very well, but if it's a 301 issue, I think you can directly implement this URL rewrite in the Apache configuration.

gitea-mirror commented

2026-05-05 13:58:13 -06:00

Author

Owner

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

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

@github-actions[bot] commented on GitHub (Jan 7, 2024): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.