Bad Gateway in Traefik docker installation

Install / Update Deployment
1

Hi I recently deployed erpnext via docker on a VPS. I set up the .env file and ran the docker-compose command from the docs. However all I get is this when I try to access the site. I have checked the site-creation container and have not found any errors. I also made sure there weren’t any firewall issues on the host machine. This appears to be a Traefik error. Screenshot below
Screenshot%20from%202022-03-03%2013-43-57
Here is my .env file:

LETSENCRYPT_EMAIL=admin@example.com
ERPNEXT_VERSION=v13.0.0
FRAPPE_VERSION=v13.0.0
MARIADB_HOST=mariadb
MYSQL_ROOT_PASSWORD=password
SITE_NAME=erpnext.redmaus.io
SITES=`erpnext.redmaus.io`
DB_ROOT_USER=root
ADMIN_PASSWORD=password
INSTALL_APPS=erpnext
ENTRYPOINT_LABEL=traefik.http.routers.erpnext-nginx.entrypoints=websecure
CERT_RESOLVER_LABEL=traefik.http.routers.erpnext-nginx.tls.certresolver=myresolver
HTTPS_REDIRECT_RULE_LABEL=traefik.http.routers.http-catchall.rule=hostregexp(`{host:.+}`)
HTTPS_REDIRECT_ENTRYPOINT_LABEL=traefik.http.routers.http-catchall.entrypoints=web
HTTPS_REDIRECT_MIDDLEWARE_LABEL=traefik.http.routers.http-catchall.middlewares=redirect-to-https
HTTPS_USE_REDIRECT_MIDDLEWARE_LABEL=traefik.http.middlewares.redirect-to-https.redirectscheme.scheme=https
SKIP_NGINX_TEMPLATE_GENERATION=0
WORKER_CLASS=gthread

Does anyone know why I am getting the bad gateway error? I would appreciate any help or advice.
Thanks

2 
docker ps

to know which containers are running.

3

Here you go:

Screenshot%20from%202022-03-03%2017-36-14
Screenshot%20from%202022-03-03%2017-36-142042×276 66.2 KB

4

use the v13.20.0

version 13.15.1 onwards the container port changed from 80 to 8080

for old image to work you’ll need to change the port here

or just use the new image.

5

Changing to v13.20.0 left me with the same bad gateway error after docker-compose up -d would I have to kill and rm all the containers first?
Thank you for your help thus far, I appreciate it!

6

stop containers
docker system prune
docker volume prune
start containers

these steps will reset everything.

make sure new image is pulled and used for the containers.

1 Like
7

This worked! I think my problem is where you mentioned pulling the new image. Thanks so much!