Beanstalkd Console

What is Beanstalkd Console?

Beanstalk Console is a small PHP web UI for inspecting a running Beanstalkd server: tubes, queued/reserved/buried jobs, and worker connections. Laradock builds it from source and serves it with PHP's built-in server. It's a companion to the beanstalkd service, not a queue server itself.

Start Beanstalkd Console

Laradock CLI

./laradock start beanstalkd-console

Docker Compose

docker compose up -d beanstalkd-console

The container depends_on the beanstalkd service in compose.yml (which in turn depends_on php-fpm), so Compose starts both automatically. A single command brings up the whole chain.

Stop Beanstalkd Console

Laradock CLI

./laradock stop beanstalkd-console

Docker Compose

docker compose stop beanstalkd-console

It holds no data of its own (it only reads from beanstalkd), so there's nothing to lose. To delete the container entirely:

Laradock CLI

./laradock remove beanstalkd-console

Docker Compose

docker compose rm -sf beanstalkd-console

Configuration

All settings live in beanstalkd-console/defaults.env and can be overridden by adding the same line to your own .env:

Variable	Default	What it does
BEANSTALKD_CONSOLE_HOST_PORT	2080	Host-side port the console UI is published on (host:2080).

Connect the console to Beanstalkd

1. Make sure the beanstalkd service is running (Compose starts it automatically via depends_on, but it needs to be reachable).
2. Open http://localhost:2080 (or your custom BEANSTALKD_CONSOLE_HOST_PORT).
3. Add a server in the UI with host beanstalkd and port 11300, the container name and internal port Beanstalkd listens on inside the Laradock network.

The console doesn't auto-discover Beanstalkd on modern Docker networks, so this manual step is required every time you start from a fresh container (the added server isn't persisted anywhere on disk).

Update the console

The Dockerfile pulls the master branch of ptrofimov/beanstalk_console fresh at build time rather than pinning a version. To pick up upstream fixes/changes, rebuild with no cache:

Laradock CLI

./laradock rebuild beanstalkd-console

Docker Compose

docker compose build --no-cache beanstalkd-console

--no-cache matters here: without it, Docker may reuse a cached layer from the last time the source was fetched instead of downloading the current master.

View logs

Useful when the page won't load or shows a blank screen:

Laradock CLI

./laradock logs beanstalkd-console

Docker Compose

docker compose logs --tail=100 beanstalkd-console

Common issues

• No server configured on first load. The console doesn't auto-discover Beanstalkd; add the server manually (host beanstalkd, port 11300) as described above.
• Can't reach beanstalkd from the console. Both containers must be on the same Compose network (they are, by default, on backend) and beanstalkd must actually be running: docker compose ps beanstalkd.
• Port already in use on your host. Another service is bound to 2080. Change BEANSTALKD_CONSOLE_HOST_PORT in .env and restart: ./laradock restart beanstalkd-console.
• Blank page or 502 after starting. The container needs beanstalkd up first; if you started beanstalkd-console alone before Compose finished bringing up beanstalkd, give it a few seconds and refresh.

---

Need the queue server itself? See Beanstalkd. New to Laradock? Start at Getting Started.