this post was submitted on 02 Apr 2025
20 points (88.5% liked)

Selfhosted

45411 readers
312 users here now

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!

founded 2 years ago
MODERATORS
 

Hello everyone.

I bought domain name (example.com) from https://njal.la/ and I want to direct it to my server but I need help with it.

Let's say that I have public and static home IPv4 address 10.172.172.172 (example) and on that address is a computer running on 192.168.200.101 (example) and there is jellyfin server (port 1020/tcp), immich server(port 1021/tcp) and bitwarden server (port 1022/tcp).

My question is can I create a subdomain and point it to these servers?

Like; jellyfin.example.com -> 192.168.200.101:1020

immich.example.com -> 192.168.200.101:1021

bitwarden.example.com -> 192.168.200.101:1022

Or do I have to buy two more separate domains for these servers? Like example2.com and example3.com?

Sorry for english and also if this is a stupid question but I need to know. I have never so far used domains and never dabbled in dns setting and I don't know where to search for info.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 2 days ago (4 children)

You run a proxy on your server (the easiest is "nginx proxy manager" that has a nice web UI), then open your router to port 80 and 443 to nginx proxy manager (NOT the web UI configuration port!)

Then you instruct the proxy to route the traffic according to the URL.

Someone coming to 10.172.172.172 with no URL? Drop the connection.

Someone going to if.example.com? Forward to 192.168:8080 and so on

[–] [email protected] 1 points 2 days ago (3 children)

And what should i set in the domain settings on https://njal.la/?

[–] [email protected] 4 points 2 days ago (2 children)

Set the A record to your IP address and CNAME to @ to all the subdomains you need

[–] [email protected] -1 points 2 days ago (1 children)

Would it be okay to contact you via signal/simplex or any messaging app for help if I'll have more very specific questions?

[–] [email protected] 1 points 1 day ago

I'm an amateur, not a professional