mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #3441] frp always transfers my request from 443 to 80 port. #2757
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#2757
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 @Kidsunbo on GitHub (May 14, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3441
Bug Description
I use frp to expose my website to public for testing. I would like to serve 80 and 443 port.
On the local machine, I start nginx to listen to 80 and 443 with SSL certificate signed to the domain. I found that the requests are always transfer to 80 port even I type https in the browser. After I delete the 80 port server block, it reports 404. So how could I transfer to 443?
frpc Version
0.48.0
frps Version
No idea, it's some free node.
System Architecture
Linux arm
Configurations
[kies_cf_http]
type = http
local_ip = 192.168.0.106
local_port = 80
custom_domains = kies.cf
host_header_rewrite = kies.cf
[kies_cf_https]
type = https
local_ip = 192.168.0.106
local_port = 443
custom_domains = kies.cf
host_header_rewrite = kies.cf
Logs
No response
Steps to reproduce
...
Affected area
@fatedier commented on GitHub (May 15, 2023):
It depends on your nginx configuration.
@Kidsunbo commented on GitHub (May 15, 2023):
Yeah sure. But I am sure that the nginx configuration is ok. I can access both 80 and 443 in my local network. I guess it's caused by cloudflare. I will test it again. Thanks.