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.

zelifcam
link
fedilink
English
15d

it’d be nice to be able to use a domain instead.

If your looking to access it outside your LAN, you’re gonna want to open up the correct ports on your router’s firewall.

@Dust0741@lemmy.world
creator
link
fedilink
English
1
edit-2
5d

No I’m not.

I have tailscale setup for external access. (I have dns records already in my domain provider pointing to a tailscale ip, so a device on my tailnet can access my domain. ie an authorized tailscale device can access nginx.example.com)

I want to know what I have to do to get minecraft.example.com to resolve interenally.

zelifcam
link
fedilink
English
2
edit-2
5d

I have to admit, I’m a bit confused.

I have dns records already in my domain provider pointing to a tailscale ip

I want to know what I have to do to get minecraft.example.com to resolve interenally.

Since your domain resolves to an internal private Tailscale IP and your question is how to access using the domain, locally…. I feel like there’s an error in your architecture here. Wouldn’t any device that is on your Tailscale private network already have access using the domain name? If by “resolve internally” you mean hosts on your LAN, not connected to Tailscale scale? How would that be possible if it resolves to a Tailscale IP. If you have control of your DNS on your LAN, you could simply add an override and point it to the LAN address of the Minecraft server.

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