nginx-proxy-manager
nginx-proxy-manager copied to clipboard
502 response error installing Nginx Proxy Manager
I am using OpenMediaVault 6.0.17 with Portainer 2.11.1. I try installing nginx proxy manager Version 3 and 2 but I get 502 response error. I the script below:
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
# These ports are in format <host-port>:<container-port>
- '80:80' # Public HTTP Port
- '443:443' # Public HTTPS Port
- '81:81' # Admin Web Port
# Add any other Stream port you want to expose
# - '21:21' # FTP
environment:
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: "npm"
DB_MYSQL_PASSWORD: "npm"
DB_MYSQL_NAME: "npm"
# Uncomment this if IPv6 is not enabled on your host
# DISABLE_IPV6: 'true'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
depends_on:
- db
db:
image: 'jc21/mariadb-aria:latest'
restart: unless-stopped
environment:
MYSQL_ROOT_PASSWORD: 'npm'
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'npm'
MYSQL_PASSWORD: 'npm'
volumes:
- ./data/mysql:/var/lib/mysql
but I got https://i.imgur.com/z0h4JnI.png
Note that I'm new to Nginx Proxy Manager, OpenMediaVault and Portainer. I followed this video for reference: https://www.youtube.com/watch?v=P3imFC7GSr0
Thanks for your help
A ton of people have this issue right now, with no apparent cause in common. Look here to see if any of this helps: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1769
I found an other solution to get arround without using OpenMediaVault 6.0.17 with Portainer 2.11.1 only with docker by following this video: https://www.youtube.com/watch?v=jp7zqjNhTAs&lc=Ugw5uUuASebELeBuydl4AaABAg.9_2IwP3MDXV9_2qiDxws7x
Litle late, but you'll notice your nginx docker install script is trying to forward host ports 80 and 443 through to the nginx docker container. By default, OMV already uses ports 443 and 80 - so when nginx tries to "claim" them to forward them you will get a port reuse error.
You'll have to have OMV work on non-standard ports, then set up the nginx docker container, and then use the nginx proxy-manager to forward the OMV FQDN/URL to the new address. I.E. instead of using port 443 for OMV, use port 4443. After the nginx proxy-manager is functioning you can tell it to forward omv.whatever to the OMV IP and port 4443.
Issue is now considered stale. If you want to keep it open, please comment :+1: