Not booting after 1.33 update

Technical Help
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

Tried to update from 1.32.5

If you are self-hosting, which installation method do you use to run Baserow?

Synology portainer, latest version. x86 32gb ram.

What are the exact steps to reproduce this issue?

Full log - 2025-05-13 19:42:43,386 INFO stopped: celeryworker (exit status 0)2025-05-13 1 - Pastebin.com

2025-05-13 19:42:43,386 INFO reaped unknown pid 165 (exit status 0)
2025-05-13 19:42:43,386 INFO reaped unknown pid 165 (exit status 0)
[BACKEND][2025-05-13 19:42:43] 127.0.0.1:43938 - “GET /api/_health/ HTTP/1.1” 200
[BACKEND][2025-05-13 19:42:43] [2025-05-13 19:42:43 +0000] [109] [INFO] Handling signal: term
[BACKEND][2025-05-13 19:42:43] [2025-05-13 19:42:43 +0000] [347] [INFO] Shutting down
[BACKEND][2025-05-13 19:42:43] [2025-05-13 19:42:43 +0000] [347] [INFO] Error while closing socket [Errno 9] Bad file descriptor
[BACKEND][2025-05-13 19:42:43] [2025-05-13 19:42:43 +0000] [346] [INFO] Shutting down
[BACKEND][2025-05-13 19:42:43] [2025-05-13 19:42:43 +0000] [346] [INFO] Error while closing socket [Errno 9] Bad file descriptor
[BACKEND][2025-05-13 19:42:43] [2025-05-13 19:42:43 +0000] [345] [INFO] Shutting down
[BACKEND][2025-05-13 19:42:43] [2025-05-13 19:42:43 +0000] [345] [INFO] Error while

2

Hey @ihoststuff, I’m sorry to hear that you’re having problems. It seems that there is a problem with the Caddyfile. Are making any changes to that by any chance? If not, then I recommend trying to upgrade to the latest version 1.33.2 instead of 1.33.0.

3

Ineed. As i manually updated the dockerimage to latest 1.33.2 it seemed to be fine. Just in case removed the caddy folder as well to force it to default.

4

Glad to hear that it’s working now!