mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #3241] how expose local website http to https in frp server #2602
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#2602
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 @thomazr on GitHub (Jan 6, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3241
Bug Description
Hello guys! I'm trying to expose a local http site to a frp server using https but I'm not succeeding. my frpc.ini looks like this:
[common]
server_addr = 137.184.181.209
server_port = 7000
[https]
type = https
local_port = 8080
custom_domains = api.tiggomark.com.br
and my frps.ini (on the server) looks like this:
[common]
bind_port = 7000
vhost_http_port = 9888
vhost_https_port = 7001
However, even having an ssl certificate installed for the api.tiggomark.com.br domain, when I try to access the address https://api.tiggomark.com.br:7001 I cannot access the address (certificate error), using the tables settings for http, works normally. Can anyone help me? Thanks!
frpc Version
0.46.0
frps Version
0.46.0
System Architecture
linux/amd64
Configurations
Sever:
[common]
bind_port = 7000
vhost_http_port = 9888
vhost_https_port = 7001
Client:
[common]
server_addr = 137.184.181.209
server_port = 7000
[https]
type = https
local_port = 8080
custom_domains = api.tiggomark.com.br
Logs
No response
Steps to reproduce
...
Affected area
@Becods commented on GitHub (Jan 7, 2023):
Enable HTTPS for local HTTP(S) service
@github-actions[bot] commented on GitHub (Feb 7, 2023):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.