NginxProxyManager / NginxProxyManager/nginx-proxy-manager
first login with 502 bad gateway,what should I do
Open
Nobody has claimed this yet.
bug
stale
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
this is my docker-compose.yml file
version: '3'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '81:81'
- '443:443'
environment:
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: "npm"
DB_MYSQL_PASSWORD: "(PASSWORD)"
DB_MYSQL_NAME: "npm"
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
db:
image: 'jc21/mariadb-aria:latest'
restart: unless-stopped
environment:
MYSQL_ROOT_PASSWORD: '(PASSWORD)'
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'npm'
MYSQL_PASSWORD: '(PASSWORD)'
volumes:
#- ./data/mysql:/var/lib/mysql
- ./mysql:/var/lib/mysql
when I login with admin@example.com and changeme,I revieve the 502 bad gateway,how can i resolve it?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the docker-compose.yml shown in the issue and inspect the app and db container logs, especially their connectivity and configured credentials. Compare the published ports and database environment variables with the container status. Done means the initial admin login no longer returns a 502 response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, mariadb, nginx
- Domain
- backend, databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100