I use Crafty Controller for Minecraft.
I have a server running at 192.168.50.16:25540.
I want it to resolve to minecraft.example.com.
I have Nginx Proxy Manager setup for my domain and can access it from inside my network, but it’d be nice to be able to use a domain instead.
NPM only has options for http and https, so is this even possible using NPM?
EDIT: this is for only internal access I have external access via tailscale.
Port forwarding is what you’re looking for. You almost certainly can configure that in your router. You tell it what the port in the outside should be and to what IP and port in your LAN it should go.
Edit: Just saw your other comments. I’m a bit at a loss.
Keep in mind that you can’t route tcp by hostname, because hostname is not a property of tcp. It only knows IP addresses. Host routing requires a protocol like HTTP.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
selfh.st Newsletter and index of selfhosted software and apps
With Crafty you can bind a specific port.
I use tailscale for public access, and have set it up so tailscale users can access the domain.
I guess what I’m asking for is NPM but for tcp.
Port forwarding is what you’re looking for. You almost certainly can configure that in your router. You tell it what the port in the outside should be and to what IP and port in your LAN it should go.
Edit: Just saw your other comments. I’m a bit at a loss.
Regular nginx does this just fine https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/
Keep in mind that you can’t route tcp by hostname, because hostname is not a property of tcp. It only knows IP addresses. Host routing requires a protocol like HTTP.