mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #565] nginx 转发https 无法正确显示页面 #441
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#441
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 @keramist on GitHub (Dec 15, 2017).
Original GitHub issue: https://github.com/fatedier/frp/issues/565
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)?
v0.14.1
What operating system and processor architecture are you using (
go env)?debian 9 LNMPA
Configures you used:
配置没有问题 只用FRP 穿透 http 自动跳转https 网站显示正常
Steps to reproduce the issue:
2.通过nginx 转发80 443 到frp 监听端口http8689 https8989 再到本地服务 https 显示
SSL 接收到一个超出最大准许长度的记录。 错误代码: SSL_ERROR_RX_RECORD_TOO_LONG
Describe the results you received:
Describe the results you expected:
希望完善 nginx 反代frp 正常显示https网站 的错误
同样的配置下 另外一个只用http的网站 正常
Additional information you deem important (e.g. issue happens only occasionally):
Can you point out what caused this issue (optional)
root@job:~# curl -vvv https://www.xxx.com
curl: (35) gnutls_handshake() failed: The TLS connection was non-properly terminated.
@fatedier commented on GitHub (Jan 17, 2018):
类似 #359 这样的问题不再回答, 请先自行确认 nginx 的相关配置正常,搜索相关的解决方案,如果通过排查能确认是 frp 的问题,再做反馈。