I updated my self-hosted docker instance to the latest version today as well as updated the OS.
Then restarted the system.
After that Caddy is giving an error and not starting:
root@docker-ubuntu-s-1vcpu-1gb-intel-blr1-01:~/baserow# docker-compose up -d
Starting baserow_volume-permissions-fixer_1 ...
baserow_redis_1 is up-to-date
baserow_db_1 is up-to-date
Starting baserow_caddy_1 ...
baserow_backend_1 is up-to-date
baserow_celery-export-worker_1 is up-to-date
baserow_web-frontend_1 is up-to-date
baserow_celery_1 is up-to-date
baserow_celery-beat-worker_1 is up-to-date
Starting baserow_caddy_1 ... error
Starting baserow_volume-permissions-fixer_1 ... done
tcp4 0.0.0.0:443: bind: address already in use
ERROR: for caddy Cannot start service caddy: driver failed programming external connectivity on endpoint baserow_caddy_1 (9f6f825948978bd651ba18a8ee473187b3b6f5204a9663de04a3d13e31aea943): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use
ERROR: Encountered errors while bringing up the project.
docker-compose ps :
root@docker-ubuntu-s-1vcpu-1gb-intel-blr1-01:~/baserow# docker-compose ps
Name Command State Ports
-----------------------------------------------------------------------------------------------
baserow_backend_1 /usr/bin/tini -- /bin/bash ... Up (unhealthy)
baserow_caddy_1 caddy run --config /etc/ca ... Exit 128
baserow_celery-beat-worker_1 /usr/bin/tini -- /bin/bash ... Up (healthy)
baserow_celery-export-worker_1 /usr/bin/tini -- /bin/bash ... Up (healthy)
baserow_celery_1 /usr/bin/tini -- /bin/bash ... Up (healthy)
baserow_db_1 docker-entrypoint.sh postgres Up (healthy) 5432/tcp
baserow_redis_1 docker-entrypoint.sh redis ... Up (healthy) 6379/tcp
baserow_volume-permissions-fixer_1 docker-entrypoint.sh chown ... Exit 0
baserow_web-frontend_1 /usr/bin/tini -- /bin/bash ... Up (healthy)
It looks like you already have another service binded to port 443. If you don’t need to use the Baserow Caddy service to manage SSL then you can instead launch the docker-compose with
WEB_FRONTEND_SSL_PORT=4443 docker-compose up -d
Or some other free port.
Alternatively you could add the above line to your .env file so you don’t need to remember to include it every time you docker-compose up.
Hm, the unhealthy there means that the custom healthcheck we’ve added in the docker-compose for Caddy isn’t working. Are you able to access and use Baserow? If so then its a problem with the healthcheck and can be safely ignored.
When you say primary user credentials is this an account you’ve already made in Baserow? If so how were you running Baserow previously and what version were you running?
Yes I would never ever recommend running that last prune command as it is very likely that it deleted all of your data. I’m not sure if it is recoverable .