Selfhosted

46653 readers

296 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:

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
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

164

[SOLVED] ELI5: How to put several servers on one external IP? (lemmy.today)

submitted 5 days ago* (last edited 5 days ago) by Allero@lemmy.today to c/selfhosted@lemmy.world

107 comments fedilink hide all child comments

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 3) 7 comments

sorted by: hot top controversial new old

[–] Onomatopoeia@lemmy.cafe 1 points 5 days 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 5 days ago* (last edited 5 days 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 5 days ago* (last edited 5 days 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)

load more comments