this post was submitted on 19 Jun 2025
163 points (98.8% liked)

Selfhosted

48981 readers
2080 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
 

I'm pretty new to selfhosting and homelabs, and I would appreciate a simple-worded explanation here. Details are always welcome!

So, I have a home network with a dynamic external IP address. I already have my Synology NAS exposed to the Internet with DDNS - this was done using the interface, so didn't require much technical knowledge.

Now, I would like to add another server (currently testing with Raspberry Pi) in the same LAN that would also be externally reachable, either through a subdomain (preferable), or through specific ports. How do I go about it?

P.S. Apparently, what I've tried on the router does work, it's just that my NAS was sitting in the DMZ. Now it works!

(page 2) 50 comments
sorted by: hot top controversial new old
[–] jacksquat@what.forfi.win 2 points 1 week ago (10 children)

Honestly Cloudflare Tunnels could be a very simple way to do it. I've always had tremendous luck with it. By using CF you can let them do all the heavy lifting instead of hosting your own... as long as you trust them.

load more comments (10 replies)
[–] thelittleblackbird@lemmy.world 2 points 1 week ago (1 children)

If you have a prosumer router I suggest you to use the ddns in the router plus a reverse proxy. This would be the cleanest solution.

If you can not, once everything is working with your external access to the synology, the dsm has a built-in reverse proxy so it can redirect http requests to another server. Although this proxy is really simple and limited it can get the work done if you setup is simple enough.

[–] Allero@lemmy.today 1 points 1 week ago* (last edited 1 week ago) (1 children)

Thanks! Syno one didn't work properly, but I got it to work through different means

[–] thelittleblackbird@lemmy.world 2 points 1 week ago (1 children)

Check it again, I used it for years before switching to something with more features

[–] Allero@lemmy.today 1 points 1 week ago
[–] Onomatopoeia@lemmy.cafe 1 points 1 week ago (1 children)

You'll need to direct that port for the given service in the router control panel.

For your current server you have a port forwarding for that port already. Just add a port forwarding rule for the new service.

[–] Allero@lemmy.today 1 points 1 week ago* (last edited 1 week ago) (1 children)

Tried doing that - here's how I've set it up:

Expected behavior: now when I enter :8100, I reach 192.168.0.113:81

Real behavior: connection times out

[–] rtxn@lemmy.world 1 points 1 week ago* (last edited 1 week ago) (3 children)

Stupid question, but is the service reachable at all? What if you map 81 to 81? Or whichever port the other, confirmed-to-work service uses? What if you map that other service to 8100?

load more comments (3 replies)
[–] bruhduh@lemmy.world 1 points 1 week ago (1 children)

NAT translation, i use my openwrt router for that

[–] possiblylinux127@lemmy.zip 1 points 1 week ago

OpenWRT also has great IPv6 support

load more comments
view more: ‹ prev next ›