Qinglong embeds Sentry for error telemetry, which triggers constant requests to o1098464.ingest.sentry.io. Here’s a simple way to block that by replacing the container entrypoint with a tiny shell script that disables the Sentry loader.
Table of contents
Open Table of contents
Why
As of 2024‑09‑15 (Qinglong 2.17.11), there’s no built‑in switch to opt out of Sentry. On my network, AdGuardHome’s blocklist spammed entries for o1098464.ingest.sentry.io, and the extra DNS traffic is unnecessary.
A solution was mentioned in a GitHub issue, but without concrete steps. This post walks through a cleaner approach: tweak docker-compose and use a small shell script so Qinglong stops sending Sentry tracking requests at startup.
docker‑compose.yml changes
- Create a
remove-tracking.shnext to yourdocker-compose.yml:
#!/bin/sh
# If already patched, run the original entrypoint
if grep -q "return;" /ql/static/build/loaders/sentry.js; then
echo "File already modified, starting normally"
exec ./docker/docker-entrypoint.sh
else
echo "File not modified, applying changes and restarting"
sed -i '/Sentry\.init/ s/^/return;/' /ql/static/build/loaders/sentry.js
# Get current container ID
CONTAINER_ID=$(cat /proc/self/cgroup | grep "docker" | sed 's/^.*\///' | tail -n 1)
# Restart container so the patched JS is picked up
docker restart $CONTAINER_ID
# Exit so Docker restarts us
exit 0
fi- Update your docker‑compose service with a custom
entrypoint:
version: "3"
services:
web:
image: whyour/qinglong:latest
volumes:
- ./ql/data:/ql/data
- ./remove-tracking.sh:/ql/remove-tracking.sh
ports:
- "5700:5700"
restart: unless-stopped
entrypoint: ["/bin/sh", "/remove-tracking.sh"]After docker-compose up -d, Qinglong will stop sending Sentry telemetry.