6
Safer to host NPM on a VPS?
(lemmy.donmcgin.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Jun 2023
6 points (100.0% liked)
Selfhosted
60831 readers
1091 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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
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.
-
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:
- 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 3 years ago
MODERATORS
Are you sure it's abandoned? The docker page was last updated three days ago and there is activity on the github page. Are they just updating the software without pushing any security fixes? I've definitely not had issues renewing certificates
There are nearly 1000 open issues and a couple of them are about potential vulnerabilities where the repeated refrain is 'we tried to contact the developer, but there's no response' which makes me... uncomfortable, especially given that NPM was the gatekeeper to a lot of services on my local network.
The cert error is related to outdated python code in the latest shipping version, https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2912 and 2921.
Again, you CAN work around it but the whole radio silence on issues and ongoing issues just makes me uncomfortable with the project and exceedingly reluctant to continue using it because it's unclear what's going on, and why.
Thank you for explaining and for the examples, it's definitely time to start learning caddy. I liked npm for the simple gui, but security and reliability are more important
the problems mentioned by @cstine@lemmy.uncomfortable.business are what lead me to try Caddy.. there's no fancy gui but it does "just work" once you figure out the caddyfile..