[GH-ISSUE #3273] How do route/IP/domain configuration directives work? #2623

Closed
opened 2026-05-05 13:41:36 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @ylluminate on GitHub (Jan 28, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3273

Bug Description

On an frps server with a well crafted frps.ini configuration file, I am finding a lot of strange traffic that comes in to various attempted efforts to penetrate various file paths, etc.

I would like to create specific rules/routes for various inbound garbage that comes into the FRP server, is this possible?

I have seen some various options that seem that frps.ini might be able to have [route] or [somedomainname.com] with perhaps custom directives such as a redirect or multiple custom_404_page directives...

Is there some documentation about these that I'm missing that's not covered in the https://github.com/fatedier/frp/blob/dev/conf/frps_full.ini example?

frpc Version

0.46.1

frps Version

0.46.1

System Architecture

linux/amd64

Configurations

Any

Logs

No response

Steps to reproduce

...

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @ylluminate on GitHub (Jan 28, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3273 ### Bug Description On an `frps` server with a well crafted `frps.ini` configuration file, I am finding a lot of strange traffic that comes in to various attempted efforts to penetrate various file paths, etc. I would like to create specific rules/routes for various inbound garbage that comes into the FRP server, is this possible? I have seen some various options that seem that `frps.ini` might be able to have `[route]` or `[somedomainname.com]` with perhaps custom directives such as a `redirect` or multiple `custom_404_page` directives... Is there some documentation about these that I'm missing that's not covered in the `https://github.com/fatedier/frp/blob/dev/conf/frps_full.ini` example? ### frpc Version 0.46.1 ### frps Version 0.46.1 ### System Architecture linux/amd64 ### Configurations Any ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [X] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:41:36 -06:00
Author
Owner

@fatedier commented on GitHub (Jan 29, 2023):

I think you'd better deploy a nginx before frps to achieve your requirements.

frp doesn't support all l7(HTTP) features.

<!-- gh-comment-id:1407688281 --> @fatedier commented on GitHub (Jan 29, 2023): I think you'd better deploy a nginx before frps to achieve your requirements. frp doesn't support all l7(HTTP) features.
Author
Owner

@ADMrugacz commented on GitHub (Feb 4, 2023):

frp docs are confusing

<!-- gh-comment-id:1416801140 --> @ADMrugacz commented on GitHub (Feb 4, 2023): frp docs are confusing
Author
Owner

@github-actions[bot] commented on GitHub (Mar 7, 2023):

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

<!-- gh-comment-id:1457279959 --> @github-actions[bot] commented on GitHub (Mar 7, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 7, 2023):

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

<!-- gh-comment-id:1457279962 --> @github-actions[bot] commented on GitHub (Mar 7, 2023): Issues go stale after 30d 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#2623
No description provided.