[GH-ISSUE #2655] 子域名访问404 #2117

Closed
opened 2026-05-05 13:21:38 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @quliting on GitHub (Nov 11, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2655

Bug Description

二级域名解析过了;
Client.ini

[TestDomain]
type=http
local_port=8080
subdomain=test

Server.ini

[common]
subdomain_host = quliting.com

然后,我访问:test.quliting.com
提示:404;
而面板中,也会有流量走过;

frpc Version

stilleshan/frpc latest

frps Version

fatedier/frps v0.36.2

System Architecture

docker

Configurations

没有;

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 @quliting on GitHub (Nov 11, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2655 ### Bug Description 二级域名解析过了; Client.ini [TestDomain] type=http local_port=8080 subdomain=test Server.ini [common] subdomain_host = quliting.com 然后,我访问:test.quliting.com 提示:404; 而面板中,也会有流量走过; ### frpc Version stilleshan/frpc latest ### frps Version fatedier/frps v0.36.2 ### System Architecture docker ### Configurations 没有; ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] 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:21:38 -06:00
Author
Owner

@quliting commented on GitHub (Nov 11, 2021):

Client 所在的8080是可以访问的;

<!-- gh-comment-id:966327679 --> @quliting commented on GitHub (Nov 11, 2021): Client 所在的8080是可以访问的;
Author
Owner

@github-actions[bot] commented on GitHub (Dec 12, 2021):

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

<!-- gh-comment-id:991811164 --> @github-actions[bot] commented on GitHub (Dec 12, 2021): 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#2117
No description provided.