mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #2378] Certificate handling as it would do a tunneling service #1890
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#1890
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 @hons82 on GitHub (May 6, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2378
The solution you want
I've been exploring frp to use basically as a tunnel service. This means, I'd need a way to have a valid certificate on the server through which I can connect internally to my clients which are on http or https with a self signed certificate. The https2http plugin does exactly that, but from what I understood in the documentation it is required that every client has a copy of the server certificate and the private server key.
That's not what I need, as I do not want the server certificate spread over my clients.
Alternatives considered
Of course I did check the https2htto plugin for this.
@fatedier commented on GitHub (May 14, 2021):
You can deploy a nginx before frps to handle certificate and redirect HTTP requests to frp.
@github-actions[bot] commented on GitHub (Jun 29, 2021):
Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.