mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #440] 配置二级域名,客户端连接成功,但是HTTP访问失败 #331
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#331
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @claud2000 on GitHub (Aug 27, 2017).
Original GitHub issue: https://github.com/fatedier/frp/issues/440
Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.
(为了节约时间,提高处理问题的效率,不按照格式填写的 issue 将会直接关闭。)
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
What version of frp are you using (./frpc -v or ./frps -v)?
0.13.0
What operating system and processor architecture are you using (
go env)?Frps : centOS 6
Frpc : Linux (NAS)
Configures you used:
Frps.ini 配置在搬瓦工 VPS
[common]
bind_port = 7000
bind_addr = 0.0.0.0
vhost_http_port = 8080
vhost_https_port = 443
dashboard_port = 7500
dashboard_user = admin
dashboard_pwd = 123456
privilege_mode = true
privilege_token = 123456789
privilege_allow_ports = 4000-50000
log_file = /bin/frps.log
log_level = debug
max_pool_count = 5
authentication_timeout = 900
subdomain_host = domain.com
tcp_mux = true
Frpc.ini 配置在QNAP NAS
[common]
server_addr = xxx.xxx.xxx.xxx
server_port = 7000
pool_count = 5
tcp_mux = true
log_file = ./frpc.log
log_level = info
log_max_days = 3
privilege_token = 123456789
[nas]
type = http
privilege_mode = true
local_ip = 127.0.0.1
local_port = 8080
use_encryption = false
use_compression = true
subdomain = nas
#custom_domains= www.domain.com
Steps to reproduce the issue:
2 如果用科学上网方式,显示500 Internal Privoxy Error,Privoxy encountered an error while processing your request: Could not load template file no-server-data or one of its included components.
3.服务器dash board 7500 访问正常,显示客户端有连接,但没有数据
4.如果在客户端用custom_domains 直接配置域名, 可以访问内网NAS 上的web页面
Describe the results you received:
服务器日志
2017/08/27 00:19:44 [I] [service.go:83] frps tcp listen on 0.0.0.0:7000
2017/08/27 00:19:44 [I] [service.go:108] http service listen on 0.0.0.0:8080
2017/08/27 00:19:44 [I] [service.go:124] https service listen on 0.0.0.0:443
2017/08/27 00:19:44 [I] [service.go:134] Dashboard listen on 0.0.0.0:7500
2017/08/27 00:19:44 [I] [main.go:112] Start frps success
2017/08/27 00:19:44 [I] [main.go:114] PrivilegeMode is enabled, you should pay more attention to security issues
2017/08/27 00:19:50 [I] [service.go:230] client login info: ip [180.162.141.127:50292] version [0.13.0] hostname [] os [linux] arch [arm]
2017/08/27 00:19:50 [I] [proxy.go:223] [dd4242adcbc4ac08] [nas] http proxy listen for host [nas.xxxxx.com] location []
2017/08/27 00:19:50 [I] [control.go:318] [dd4242adcbc4ac08] new proxy [nas] success
客户端日志
2017/08/27 12:19:53 [I] [control.go:276] [dd4242adcbc4ac08] login to server success, get run id [dd4242adcbc4ac08]
2017/08/27 12:19:53 [I] [control.go:411] [dd4242adcbc4ac08] [nas] start proxy success
2017/08/27 12:26:41 [E] [control.go:178] [dd4242adcbc4ac08] work connection closed, broken pipe
2017/08/27 12:26:41 [W] [control.go:321] [dd4242adcbc4ac08] read error: broken pipe
2017/08/27 12:26:41 [I] [control.go:339] [dd4242adcbc4ac08] control writer is closing
Describe the results you expected:
客户端直接配置域名可以用,但是我想在NAS 上开两个http 服务, 一个用于NAS web 管理, 一个用于个人网站。所以想使用二级域名。但是一直不成功
域名domain.com 是在godaddy买的 ,dns 已经映射到服务器IP
Additional information you deem important (e.g. issue happens only occasionally):
Can you point out what caused this issue (optional)
@claud2000 commented on GitHub (Aug 27, 2017):
已解决, 原来二级域名要先做cname 解析