502 Bad gateway after update

[aik]

I updated my containers as usual, all went through fine, but opening the webui at http://srv:81 returns "502 bad gateway". How to debug this kind of problems?

mediacms_web_1's /etc/nginx/sites-available/default suggests "uwsgi_pass 127.0.0.1:9000" might be a problem.

I quickly googled, says uwsgi wants a newer python but I'd think the containter images should have this fixed? Any hints?

Ubuntu 24.04.3 LTS, I have not updated it in a few months so it cannot be it, I think.

Here is the update process:

aik@srv ~ [SIGINT]> ./mediacms.sh
+ cd /home/aik/mediacms
+ docker pull mediacms/mediacms
Using default tag: latest
latest: Pulling from mediacms/mediacms
Digest: sha256:e80156c9079e1581279619134abb880a98ff2532bac13b863ab9c5d45c942d67
Status: Image is up to date for mediacms/mediacms:latest
docker.io/mediacms/mediacms:latest
+ docker-compose down
WARNING: The POSTGRES_DB variable is not set. Defaulting to a blank string.
WARNING: The POSTGRES_USER variable is not set. Defaulting to a blank string.
Stopping mediacms_celery_worker_1 ... done
Stopping mediacms_web_1           ... done
Stopping mediacms_celery_beat_1   ... done
Stopping mediacms_redis_1         ... done
Stopping mediacms_db_1            ... done
Removing mediacms_celery_worker_1 ... done
Removing mediacms_web_1           ... done
Removing mediacms_migrations_1    ... done
Removing mediacms_celery_beat_1   ... done
Removing mediacms_redis_1         ... done
Removing mediacms_db_1            ... done
Removing network mediacms_default
+ docker-compose -f docker-compose-aik.yaml up -d
WARNING: The POSTGRES_DB variable is not set. Defaulting to a blank string.
WARNING: The POSTGRES_USER variable is not set. Defaulting to a blank string.
Creating network "mediacms_default" with the default driver
Creating mediacms_redis_1 ... done
Creating mediacms_db_1    ... done
Creating mediacms_celery_beat_1 ... done
Creating mediacms_migrations_1  ... done
Creating mediacms_celery_worker_1 ... done
Creating mediacms_web_1           ... done

My config (which is a copy of docker-compose.yaml):

aik@srv ~> cat mediacms/docker-compose-aik.yaml                                      
version: "3"                                                                         
                                          
services:                    
  migrations:                         
    image: mediacms/mediacms:latest                                                  
    volumes:                                                                         
      - ./:/home/mediacms.io/mediacms/
      - /home/aik/mediacms_media_files/:/home/mediacms.io/mediacms/media_files/      
    environment:                                                                                                                                                          
      ENABLE_UWSGI: 'no'                                                             
      ENABLE_NGINX: 'no'                  
      ENABLE_CELERY_SHORT: 'no'           
      ENABLE_CELERY_LONG: 'no'            
      ENABLE_CELERY_BEAT: 'no'            
      ADMIN_USER: 'admin'                 
      ADMIN_EMAIL: 'admin@localhost'      
      ADMIN_PASSWORD: 'mysecretpassword'           
    command: "./deploy/docker/prestart.sh"                                           
    restart: on-failure                   
    depends_on:                           
      redis:                              
        condition: service_healthy                                                                                                                       12:34:34 [33/234]
      db:
        condition: service_healthy
  web:
    image: mediacms/mediacms:latest
    deploy:
      replicas: 1
    ports:
      - "81:80"
    volumes:
      - ./:/home/mediacms.io/mediacms/
      - /home/aik/mediacms_media_files/:/home/mediacms.io/mediacms/media_files/
    environment:
      ENABLE_CELERY_BEAT: 'no'
      ENABLE_CELERY_SHORT: 'no'
      ENABLE_CELERY_LONG: 'no'
      ENABLE_MIGRATIONS: 'no'
    depends_on:
      - migrations
  celery_beat:
    image: mediacms/mediacms:latest
    volumes:
      - ./:/home/mediacms.io/mediacms/
      - /home/aik/mediacms_media_files/:/home/mediacms.io/mediacms/media_files/
    environment:
      ENABLE_UWSGI: 'no'
      ENABLE_NGINX: 'no'
      ENABLE_CELERY_SHORT: 'no'
      ENABLE_CELERY_LONG: 'no'
      ENABLE_MIGRATIONS: 'no'
    depends_on:
      - redis
  celery_worker:
    image: mediacms/mediacms:latest
    deploy:
      replicas: 1
    volumes:
      - ./:/home/mediacms.io/mediacms/
      - /home/aik/mediacms_media_files/:/home/mediacms.io/mediacms/media_files/
    environment:
      ENABLE_UWSGI: 'no'
      ENABLE_NGINX: 'no'
      ENABLE_CELERY_BEAT: 'no'
      ENABLE_MIGRATIONS: 'no'
    depends_on:
      - migrations
  db:
    image: postgres:17.2-alpine
    volumes:
      - ../postgres_data:/var/lib/postgresql/data/
    restart: always
    environment:
      POSTGRES_USER: mediacms
      POSTGRES_PASSWORD: mediacms
      POSTGRES_DB: mediacms
      TZ: Australia/Canberra
    healthcheck:
      test: ["CMD-SHELL",  "pg_isready -d $${POSTGRES_DB} -U $${POSTGRES_USER}", "--host=db", "--dbname=$POSTGRES_DB", "--username=$POSTGRES_USER"]
      interval: 10s
      timeout: 5s
      retries: 5
  redis:
    image: "redis:alpine"
    restart: always
    healthcheck:
      test: ["CMD", "redis-cli","ping"]
      interval: 30s
      timeout: 10s
      retries: 3

[mgogoulos]

did you do a git pull too, besides updating containers? Seems that the code tries to find uwsgi that doesn't exist (was replaced with gunicorn). The default docker-compose files mount the local fs, so it overrides any changes in the containers - this will be changed at some point

[aik]

thanks!! my bad, I previously did git remote updateonly, after git pull origin/main it works now!

[aik]

buuuut now there is no media shown in the web. Folders are not emty. I am puzzled.

[mgogoulos]

make sure you're using the docker compose file you were using before, if you have been using a docker compose file with changes (eg as where the DB is saved), and you switched to another docker compose after git pull, maybe the app is now talking to a new DB. just a thought.