← Directory

Pixelserv-tls

Pixelserv-TLS is a lightweight Transport Layer Security (TLS) web server that returns a 1-pixel image for ad and tracker domains.

  • Other
  • Tools & Utilities
Pixelserv-TLS is a lightweight Transport Layer Security (TLS) web server that returns a 1-pixel image for ad and tracker domains. It is used in self-hosted Domain Name System (DNS) filtering and ad-blocking setups to reduce bandwidth and improve page load times. It supports TLS 1.0, 1.2, and 1.3, uses Server Name Indication (SNI), and automatically generates server certificates for configured domains on first use.

Platform availability

Available on 1 of 6 install platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub

Health score

14/100 Low

Maintained
0GitHub repository is archived
Popular
209 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

How is this calculated?

A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today, links checked today

GitHub stars
9
Open issues
0
Last commit
2022-02-05
Activity
stale

Checked today - source: GitHub (imTHAI/docker-pixelserv-tls)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 10 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Generate and back up the root CA Run the container once: it auto-generates a root CA certificate (retrievable at http://127.0.0.1/ca.crt). Persist the certificate folder to a host path so the root CA and the on-the-fly generated ad/tracker certificates are easy to back up. source
  • Back up the root CA The root CA certificate is generated automatically at build; retrieve it from http://127.0.0.1/ca.crt and store it on a host folder alongside the on-the-fly domain certificates so you can back it up easily. source
  • Root CA backup Run the container once to generate the root CA, then store the root and on-demand certificates in a host folder for easy backup. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How should I back up the certificates generated by the Docker image?

Run the container once, copy ca.crt and ca.key from /var/cache/pixelserv to a host folder, remove the container, and then start it again with that folder mounted at /var/cache/pixelserv. This keeps the root CA and generated ad/tracker certificates easy to back up.

Which ports do the Docker examples require?

They expose ports 80 and 443, or use host networking on Linux so the container can use the host ports directly.

How can pixelserv-tls work with Pi-hole?

It can be run alongside Pi-hole so blocked domains can show a working block page instead of only failing.

How is pixelserv-tls used with AdGuard Home?

A setup guide shows it can be used with AdGuard Home, including using its cache store to handle blocked domains.

Can Diversion install or manage pixelserv-tls on routers?

Yes, Diversion can manage pixelserv-tls installations on supported routers running Asuswrt-Merlin firmware.

Answers sourced from github.com, www.reddit.com, www.reddit.com, www.snbforums.com

Community

Collected 5 days ago - public community threads