Self-host Blocky on a VPS
DNS proxy and ad blocker with caching and conditional forwarding. The install form carries config.yml as an editable file, so it starts with a small denylist and public upstream resolvers.
levelrail-cli templates install blocky --name my-blockySpecification
- Status
- Listed
- Category
- Networking
- Services
- blocky
- Ports
- 4000, 5353
- Volumes
- 0
- Memory
- about 64 MiB
- arm64
- unknown
- amd64
- unknown
- Settings to fill in
- none
- License
- Permissive license, Apache-2.0
- Listing
- Community template
About Blocky
DNS proxy and ad blocker with caching and conditional forwarding. The install form carries config.yml as an editable file, so it starts with a small denylist and public upstream resolvers.
What it deploys
Blocky runs as one service in a single Compose app, listening on ports 4000, 5353.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| blocky | ghcr.io/0xerr0r/blocky | v0.36.0 | 4000, 5353 | none |
Before you install
- CPU architecture. arm64 unknown. The scan could not read a manifest or the tag is chosen at install time. This is not a claim either way.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
Settings and environment
The catalog lists no environment variables for this template.
First run
- Point a client at the DNS port to resolve through Blocky, then edit the config file setting to add real blocklists. The HTTP API is on port 4000.
Install Blocky on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get blocky -
Install it
This template has an install form, so the CLI fills each setting from --env, a generated secret or its default.
levelrail-cli templates install blocky --name my-blockyTo put a service behind a domain at install, add
--domain SERVICE=HOST:levelrail-cli templates install blocky --name my-blocky --domain blocky=blocky.example.com
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Blocky.
Docs and upstream
More in Networking
- CoreDNSPlugin based DNS server on the official image. The install form carries the Corefile as an editable file, so it starts as a caching forwarder with health and readiness endpoints.
- DDNS UpdaterKeeps DNS records pointed at your changing public IP for many providers, with a small web page showing each record's status. The install form carries config.json as an editable file, so you add your providers there.
- Syncthing Discovery ServerPrivate global discovery server that lets your Syncthing devices find each other without the public one. Plain HTTP mode, meant to sit behind your own TLS proxy.
- Syncthing Relay ServerPrivate relay server that carries Syncthing traffic between devices that cannot connect directly. Exposes a small status page.
- UpSnapWeb dashboard to wake, shut down and ping devices on your network, with scheduled wake ups and per device ports.