mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #4420] Bare metal / VM install instructions - not the entire world is docker #2829
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2829
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @netchild on GitHub (Mar 7, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4420
Is your feature request related to a problem? Please describe.
The world is not docker. There are use cases for it, but there are a lot of uses cases where docker is not the best solution. Just providing install instructions for docker leaves out those situations where something else than docker is required / needed / decided upon / forced, nginx runs on a lot of platforms, not only on docker. There may be unsupported architectures in use (risc-v, cheri, powerpc, ...), there may be unsupported OS in use (*BSDs), there may be a requirement that it runs in a VM (no matter if because of policy, security reasons, or whatever), and so on... where your project would run simply fine. It also prevents an OS specific package management to pickup your project as an easy package install. There may also be a security requirement that the software bill of materials is easily inspectable and that open source stuff has to be manually fixable independently from the original developer, that no pre-build image from an unknown source is allowed to be installed.
The dockerfile is not an install instruction. You are locking yourself into a niche instead of opening yourself to the entire open source ecosystem.
Describe the solution you'd like
Provide bare metal install instructions (list of requirements, initial config, where to install what from your repo).
@B0F1B0 commented on GitHub (Mar 9, 2025):
Hi netchild,
if you have Proxmox, you can easy install
NPM - Nginx Proxy Managerin an LXC Container with the[Proxmox VE Helpder-Scripts](https://community-scripts.github.io/ProxmoxVE/scripts?id=nginxproxymanager).Default settings:
OS: Debian 12
CPU: 2vCPU
RAM: 1GB
HDD: 4GB
The Proxmox VE Helper script executes this script, among others.
I have adapted this script that the following script will do perform a "bare metal" installation (Version 2.12.3).
Since I am currently still on version 2.11.3 and would like to upgrade to 2.12.XXX, but version 2.12.3 (latest) is not working properly for me (streams not working), I also added version 2.12.0 till 2.12.2 as a comment in the script.
Search for Keyword:
######LATETEST RELEASEthere you can comment out/in the necessary Version.__--There we have the salad --__🤗@mokhos commented on GitHub (Mar 11, 2025):
Hi @B0F1B0,
may I ask if your setup works at all?
I'm using the latest version of NPM through the PVE Helper Scripts. But the proxy hosts are not working with my custom-ssl.
I even tried it without SSL, but the hosts are being redirects to https for some unknown reason and I get some ssl invalid end of file error.
I'm confused. I checked my configuration several times but I don't know if the problem is with the npm or not.
@B0F1B0 commented on GitHub (Mar 11, 2025):
Hi @mokhos
The latest PVE Helper Scripts install Version 2.12.3 and with that, i had no trouble with proxy-host and Let's Encrypt Certificates.
I did not use any custom ssl.
I had trouble with streams, so at the moment i am testing 2.12.2. There i had no trouble at the moment.
i even testet 2.12.3 without SSL-Certificates and it also worked, but only with firefox, because brave allways wants https.
@o10g commented on GitHub (Apr 8, 2025):
Hi @B0F1B0
Could you be so kind to provide instructions how to downgrade the Proxmox installation to 2.12.2, as I need to proxying streams and the latest version has a problem with it -
500 Internal System Error:@B0F1B0 commented on GitHub (Apr 9, 2025):
Hi @o10g
I tried to downgrade NPM 2.12.3 to 2.12.2 but this does not work properly.I cant Login anymore.
The only solution I see here is to manually install NPM 2.12.2 in an LXC container as described above.
OS: Debian 12
CPU: 2vCPU
RAM: 1GB
HDD: 4GB
Here is the script from above, which explicitly installs NPM 2.12.2.
@Wolfhound905 commented on GitHub (Apr 28, 2025):
@o10g @B0F1B0
Streams is having an issue because you need a higher version of node. 17.9.1 works.
The error is
structuredClone is not defined, which was a function added in node v17. So make sure to updatenpm.serviceto use like nvm 17 path and not usr/bin/node. Let me know if you need help, this got my streams working on Proxy Manager v2.12.3@PontyJohnty commented on GitHub (May 12, 2025):
I am running 2.12.3 from proxmox helper scripts. on an unpriv LXC on Proxmox.
If this is of any help i did the following to get streams working.
confirmed node version
node -vfor me it was v24.0.1
then i updated the npm.service unit ( /lib/systemd/system/npm.service ) to the following
Note the former ExecStart is commented out for reference.
Ensure your node version matches that on the ExecStart line.
I was then able to create streams.
@LohmarCoUk commented on GitHub (Nov 11, 2025):
I have to agree with 'not the entire world is docker' - for example I use a Ubuntu LXD/LXC environment. I could run a docker or podman container inside my LXC container but what is the point of having a box in a box?
I'm considering to publish a git-repository for 'Nginx Proxy Manager on Bare Metal' - share your thoughts on this.
Here my Script (NPM Version 2.13.2), it should work on Bare Metal / VMs / and Container.