this post was submitted on 01 Nov 2025
41 points (97.7% liked)

Selfhosted

60896 readers
736 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
 

I'm currently using NPM and upgrading to a new VPS for my business. I have a public website and am going to host a few more for friends, plus a few other services. Everything is on docker for ease. I use Cloudflare for DNS so would prefer using a DNS challenge. I will change this at some point but not yet ready to!

Should I:

  1. stick with Nginx Proxy Manager which I know well (is it really that insecure or outdated?)
  2. switch to NPM Plus (assuming this is the easiest)
  3. switch to Caddy (seems to be there most recommended but will be a learning curve for me)
  4. Try out Nginx (seems like a massive learning curve so I'm very reluctant)
you are viewing a single comment's thread
view the rest of the comments
[โ€“] brewery@feddit.uk 1 points 8 months ago (1 children)

Actually this happened to me about 6 months ago too - I wanted to switch to add crowdsec support but just could not get it to work so gave up and switched back to npm. I just assumed I wasn't doing it right and never got around to trying again

[โ€“] ikidd@lemmy.world 2 points 8 months ago

I thought it was pretty weird, so I tried again a while later; same result. I checked through issues and couldn't see anything, I figured it was just me. I tried because NPM was just full of error logs and was having some sort of shitfit, so I blew it out and rebuilt from scratch, now all is fine. But the NPM+ defeated me. I might have to try again just because.