Docker Nextcloud 500 accessing status.php after upgrade to 20.0.3.2 via watchtower

This is my compose:

version: β€˜3’
services:
db:
image: mariadb
command: --transaction-isolation=READ-COMMITTED --binlog-format=ROW
restart: always
volumes:
- db:/var/lib/mysql
environment:
- MYSQL_ROOT_PASSWORD=
env_file:
- db.env

redis:
image: redis:alpine
restart: always
command: redis-server --requirepass

app:
image: nextcloud:apache
restart: always
volumes:
- nextcloud:/var/www/html
- host_data_dir:/var/www/html/data
environment:
- VIRTUAL_HOST=redacted.redacted.io
- LETSENCRYPT_HOST=redacted.redacted.io
- LETSENCRYPT_EMAIL=redacted@gmail.com
- MYSQL_HOST=db
- REDIS_HOST=redis
- REDIS_HOST_PASSWORD=
env_file:
- db.env
depends_on:
- db
- redis
networks:
- proxy-tier
- default

cron:
image: nextcloud:apache
restart: always
volumes:
- nextcloud:/var/www/html
entrypoint: /cron.sh
depends_on:
- db
- redis

proxy:
build: ./proxy
restart: always
ports:
- 80:80
- 443:443
labels:
com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: β€œtrue”
volumes:
- certs:/etc/nginx/certs:ro
- vhost.d:/etc/nginx/vhost.d
- html:/usr/share/nginx/html
- /var/run/docker.sock:/tmp/docker.sock:ro
networks:
- proxy-tier

letsencrypt-companion:
image: jrcs/letsencrypt-nginx-proxy-companion
restart: always
volumes:
- certs:/etc/nginx/certs
- vhost.d:/etc/nginx/vhost.d
- html:/usr/share/nginx/html
- /var/run/docker.sock:/var/run/docker.sock:ro
networks:
- proxy-tier
depends_on:
- proxy

volumes:
host_data_dir:
driver: local
driver_opts:
type: none
device: /mnt/Data/data
o: bind
db:
nextcloud:
certs:
vhost.d:
html:

networks:
proxy-tier:

So I had watchtower running and it pulled a new redis, nextcloud and letsencrypt image. When the containers were recreated I get 500 errors accessing the application. The only error I see in the log is in the nextcloud_proxy container with a 500 accessing status.php.

No useful logs in the nextcloud.log - the logs seem to just stop after the upgrade is completed. I tried increasing the level to debug but it doesn’t lead to any other useful input. Incidentally, I’ve noticed that I get this same 500 error if I try and recreate the containers using docker-compose up -d - for example adding a label to any of the containers. I know that my compose file is correct as I can create a nextcloud instance from scratch perfectly fine - when there are no existing volumes etc.

Any ideas?

Anybody???

did you try to restart the the proxy container? restart docker?

Thank you for your reply - I did restart docker and the proxy container. As far as I can tell, redis was upgraded also by watchtower