this post was submitted on 19 Nov 2026
33 points (100.0% liked)

Selfhosted

63910 readers
1099 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Someone: "... the new php vulnerability"

Me: "wait what, another one?"

S: "Yes"

I had exposed services for years, never a problem. I don't have time to be on top of all of this. Im going random high port wireguard access only.

top 10 comments
sorted by: hot top controversial new old
[–] JoeKrogan@lemmy.world 9 points 1 hour ago (1 children)

I do the same. It helps me sleep a little better

[–] confusedpuppy@lemmy.dbzer0.com 4 points 30 minutes ago (1 children)

I do the same, SSH behind WireGuard and my public facing website/services are on a higher port number

The only traffic I see is from myself or the people I know personally. It prevents a hobby from turning into a job

However I do feel like the response to all these vulnerabilities are getting overblown. From my understanding, a lot of them require very specific conditions for exploits to work. It seems like AI pushers are trying to pad their security resumes with fancy websites. But I'm not a security expert so I could be wrong

I instead keep my system simple and mininal to avoid any headaches or at least keep them to a minimum

[–] JoeKrogan@lemmy.world 2 points 21 minutes ago

I agree. The fear helps their IPOs. We've always had bugs. I do the same and follow a KISS approach and do defense in depth.

[–] Shameless@lemmy.world 1 points 1 minute ago

I'm honestly considering this for some of my small business customers too, expose their services other than their standard websites on high ports, that way it's generally only expected business contacts who will be making connections to those services.

AI has so many customers flapping about security at the moment.

[–] Reannlegge@lemmy.ca 5 points 55 minutes ago (2 children)

I already do this but I get nervus still with this second php thingy. Knock on wood that wireguard vulnerabities are not going to come into the thing.

[–] warmaster@lemmy.world 5 points 50 minutes ago

Everything everywhere all at once, AI will be there to take away everything.

[–] SGG@lemmy.world 1 points 8 minutes ago* (last edited 8 minutes ago)

Wireguard is a relatively speaking new technology compared to PHP. Less legacy code to worry about.

I do not doubt there will/are vulnerabilities for it, but with any luck they will be few and far between with quick patches

[–] undefinedTruth@lemmy.zip 2 points 8 minutes ago

Same here, for quite a while. There is no reason for my NextCloud server to be exposed on the public internet. I still have access to it from everything via Tailscale and it works perfectly.

[–] Semi_Hemi_Demigod@lemmy.world 1 points 51 seconds ago

I’ve been doing this since I set up remote access. Nobody else should ever be using this but me, so why bother exposing anything?

Writing iptables isn’t even that hard

[–] taco_shale032@lemmy.ml 2 points 1 hour ago

I fear this will eventually become the only way to safely selfhost for pretty much everyone. :/