8
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
8 points (100.0% liked)
Selfhosted
39683 readers
735 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 1 year ago
MODERATORS
NPM also looks abandoned right now. There’s some security patches that are not being addressed, and certificate renewal is hit or miss due to the age of NPM’s certbot vs the mainline.
If you’re deploying something new, you might want to consider caddy or nginx by itself or some other reverse proxy at this point since it really looks like the dev has vanished and nobody is taking over maintenance yet.
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..