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.

Possibly linux
link
fedilink
English
125d

No

Reverse proxies like you are talking about are only for http connections. For more information look at the OSI model. (The proxy is operating on the application layer while Minecraft is on the transport layer)

Instead use DNS to resolve the domain name to an IP. Better yet, just set a static IP.

@redxef@feddit.org
link
fedilink
English
65d

There are minecraft reverse proxies, so, yes, a http proxy will not work, but the general idea is still viable and doable with very little effort.

Set up a few domains all resolving to one IP. Run itzg/minecraft-router and use that to proxy the traffic to different servers based on the domain.

Also, they don’t even need a reverse proxy, but just resolve the domain name to the IP (in the simple case of one domain name per I0). That can be accomplished by hosting their own dns server, editing the hosts file or just pointing a public dns record at the private ip address, which will only work in their network,l.

@Dust0741@lemmy.world
creator
link
fedilink
English
25d

Thanks for the help. This is enough to get me started

You could also use nginx if you wanted; it’ll do arbitrary tcp data with the stream plugin.

Create a post

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:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 136 users / day
  • 427 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog