Maybe a port forward can do it? That's under Network -> Firewall. in the "Port forward" tab.
I'd need more info on the intended use-case and what's the requirement for a tunneling software that's making ssh tunnels and vpn tunnels unsuitable.
Maybe a port forward can do it? That's under Network -> Firewall. in the "Port forward" tab.
I'd need more info on the intended use-case and what's the requirement for a tunneling software that's making ssh tunnels and vpn tunnels unsuitable.
It's an http service running on my home server (running openwrt and docker).
SSH and VPN are either blocked or heavily throttled where i live.
If you want FRP, why not just install FRP? It even has a LuCI app to control it from what it looks like.
NGINX is also available at a mere 1kb in size for the slim version, full version also available as well as HAproxy. Those will have you more than covered, and support SSL.
Looks like there's also acme.sh support, with a matching LuCI app that can handle your SSL certificate situation as well.
FRP is fine but the https certificate part is not easy/automated.
Frp or nginx are both available on openWRT to do what you want.
You could, technically, use mTLS with Caddy.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
Fewer Letters | More Letters |
---|---|
HTTP | Hypertext Transfer Protocol, the Web |
SSH | Secure Shell for remote terminal access |
SSL | Secure Sockets Layer, for transparent encryption |
VPN | Virtual Private Network |
nginx | Popular HTTP server |
4 acronyms in this thread; the most compressed thread commented on today has 3 acronyms.
[Thread #753 for this sub, first seen 16th May 2024, 09:55] [FAQ] [Full list] [Contact] [Source code]
tailscale.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!