this post was submitted on 25 Apr 2026
52 points (96.4% liked)

Selfhosted

60093 readers
1156 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.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

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

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 7 days old, your post is exempt from this rule as long as you continue to engage in comments.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

After trying out Cosmos Cloud (and it not working for the clients), I'm back at square one again. I was going to install Docker Desktop, but I see it warns that it runs on a VM. Will this be a problem when trying to remote connect to certain services, like Mealie or Jellyfin?

you are viewing a single comment's thread
view the rest of the comments
[–] foggy@lemmy.world 4 points 2 months ago* (last edited 2 months ago) (1 children)

If it's a Linux box, everything over 1023 just needs root.

For Debian flavors,

/proc/sys/net/ipv4/ip_local_port_range

At least for those I use. Idk for rhel etc.

I can check my boxes with system ctl:

sysctl net.ipv4.ip_local_port_range

And tested on a VM, this wide s your ephemeral range:

sysctl -w net.ipv4.ip_local_port_range="1024 65535"

Manage persistence in /etc/sysctl.conf

I'll be honest here, I asked Claude for the windows equiv of that. I haven't tested. Proceed with caution:

To check:

netsh int ipv4 show dynamicport tcp

To expand ephemeral range:

netsh int ipv4 set dynamicport tcp start=10000 num=55535

Syntax makes enough sense to me, but I repeat I have not vetted this.

HOWEVER,

all moot. You have 65k ports PER CONNECTION, holmes. Sorry I'm drunk now my tones changes and typos = more :)

So you at 10.0.0.1 connect to Google at 8.8.8.8 and cloudflare at 1.1.1.1, you can use 130k connections between the two. So this isn't as useful as you may think you need it to be (idk what you're doing lol, load balancer?)

If you're churning through tons of short connections, you can "run out" of ports even though you have plenty... they're all just cooling down.

net.ipv4.tcp_tw_reuse=1

lets the kernel grab them sooner.

Claude says Windows would be

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay

That's a registry change. Proceed with extreme caution. Use a VM or throw away machine. I have absolutely not vetted the windows version here and registry edits are inherently dangerous. I usually yell at an AI that tells me to use regedit. Probably don't do this unless the system is backed up and those backups are tested.

Hope this helps your crazy load balancer or whatever :)