Install Nginx Proxy Manager on Proxmox LXC & Alpine Linux

Install Nginx Proxy Manager on Proxmox LXC & Alpine Linux


Currently the only supported way to install Nginx Proxy Manager is to run it inside of a Docker container. However, for someone like me, using Proxmox, I like to utilize LXC for my containerization. This guide will step anyone through the process of Installing Nginx Proxy Manager on a Proxmox LXC Container.

Preparation & Prerequisites

Step 1: Download the Alpine 3.16 container.

Download Alpine Linux

DO NOT USE Alpine 3.17 - Installer Will Fail Later

Step 2: Create a new LXC container using the downloaded Alpine 3.16 template.

Step 3: Log into the newly created container. Then update and upgrade the container.

apk update apk upgrade

Step 4: Next create an “npm” user on the container. It will be needed for the install script.

adduser npm

Step 5: Now run the install script.

wget --no-cache -qO - | sh

Step 6: After the install script runs you will be prompted with the login URL:

Download Alpine Linux

Save this URL and port number for later as you will need it to access the web management panel.

Step 7: Next, using your text editor of choice edit /usr/local/openresty/nginx/conf/nginx.conf

nano /usr/local/openresty/nginx/conf/nginx.conf 

You will need to comment out this line pid /run/nginx/; to # pid /run/nginx/;

Save and close the file.

Step 8: Reboot the container


Step 9: Enter the provided IP address in a browser and use the default login:

E-Mail: [email protected]
Password: changeme

Step 10: Once logged in, you will be asked to change the default admin login. Use the previously provided default login as the last login option.

Nginx Proxy Manager is now installed!

Thanks for reading!

Written By: Max Kulik

This post has been updated on 6/19/2023.


  • Install script created by Elton Renda. Further documentation for other containers and other operating systems are listed here.
  • Broken support for Alpine Linux 3.17 documented on Issue #118.
  • Script does not create the “npm” user by default and it is not documented outside of Issue #117.