502 Bad Gateway - after updating docker-compose

Support
1

I updated my Vikunja with docker-compose to the latest version.
I got the Error " 502 Bad Gateway" in the browser.
When I look in the dockers Containers from the vikunja/frontend changed, an I think there would be an error with die ports.
docker ps

old version: PORTS 80/tcp
new version: PORTS no entry

my “docker-compose.yml”

version: ‘3’

services:
db:
image: mariadb:10
command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
environment:
MYSQL_ROOT_PASSWORD: supersecret
MYSQL_USER: vikunja
MYSQL_PASSWORD: secret
MYSQL_DATABASE: vikunja
volumes:
- ./db:/var/lib/mysql
restart: unless-stopped
api:
image: vikunja/api
environment:
VIKUNJA_DATABASE_HOST: db
VIKUNJA_DATABASE_PASSWORD: secret
VIKUNJA_DATABASE_TYPE: mysql
VIKUNJA_DATABASE_USER: vikunja
VIKUNJA_DATABASE_DATABASE: vikunja
volumes:
- ./files:/app/vikunja/files
depends_on:
- db
restart: unless-stopped
frontend:
image: vikunja/frontend
restart: unless-stopped
proxy:
image: nginx
ports:
- 8022:80
volumes:
- ./nginx.conf:/etc/nginx/conf.d/default.conf:ro
depends_on:
- api
- frontend
restart: unless-stopped

Nginx.conf:

server {
listen 80;

location / {
    proxy_pass http://frontend:80;
}

location ~* ^/(api|dav|\.well-known)/ {
    proxy_pass http://api:3456;
    client_max_body_size 20M;
}

}

Can anyone help me with the error?

thanx

2

Hi, starting Vikunja version v0.23, the two containers have been merged into one, there’s no separate frontend or api anymore.

Please have a look at the v0.23 release notes, the changes are described there in detail.

1 Like