Backend won't start: 503

I am trying out browsertrix-cloud, following the local deployment guide (using k3s). Everything seems to work except browsertrix-backend.

I have set up as recommended in the docs:

helm upgrade --install btrix \
https://github.com/webrecorder/browsertrix-cloud/releases/download/v1.8.0/browsertrix-cloud-v1.8.0.tgz

And then I check the deployment:
kubectl wait --for=condition=ready pod --all --timeout=300s

But it times out because browsertrix-backend is not running.

So I checked the pod with kubectl logs and got this:

Defaulted container "api" out of: api, op
INFO:     Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)
INFO:     Started parent process [7]
INFO:     Started server process [10]
INFO:     Waiting for application startup.
INFO:     Started server process [9]
INFO:     Waiting for application startup.
Waiting DB
Waiting DB
INFO:     Application startup complete.
INFO:     Application startup complete.
INFO:     10.42.0.1:33168 - "GET /healthz HTTP/1.1" 503 Service Unavailable
INFO:     10.42.0.1:33184 - "GET /healthz HTTP/1.1" 503 Service Unavailable

(and many more lines with the same error.)

Everything else works, including the frontend, which displays a “Please wait while Browsertrix Cloud is initializing”

Any idea what the problem could be?

I figured it out: the local-mongo service wasn’t getting an ip address. I edited mongo.yaml to comment out “clusterIP: none” and now it works. Must be a problem with my setup (k3s).

1 Like