Skip to content
How to install

What leaves your server

The panel sends no telemetry, and there is no control plane. Your sites, their data and the panel’s database stay on your servers. This page lists every request the panel makes to anyone else, what each one sends, and the switch that stops it. Like any request, each one shows the service your server’s address.

Request When What it sends Switch
GitHub, api.github.com: is there a new release? Hourly, and once after an update The channel you follow, by the release it asks for. WPL7_GITHUB_TOKEN when you set one. Pause Update check on Automations → Schedules. Check now still asks.
GitHub Pages: the signed recipe catalog Hourly Nothing but the request WPL7_CATALOG_URL=off in deploy/.env, or pause Recipe catalog
php.net: PHP’s newest releases, release candidates and news Since 0.4.1 Every 15 minutes Nothing but the request Pause PHP releases on Automations → Schedules
GitHub, api.github.com: what a PHP security release fixed Once per security release Nothing but the request. WPL7_GITHUB_TOKEN when you set one. As for php.net
Each server: is there a newer site image? Every 15 minutes, as the registry asked by that server’s Docker. A server that builds its own images asks Docker Hub about its base image when php.net has a newer PHP, and pulls it for each build. Nothing but the request As for php.net
wpvulnerability.net: known vulnerabilities Once a day per slug, hourly for one it calls closed, from the inventory scan and the nightly housekeeping The slug of every installed plugin and theme, custom ones included, and each WordPress version. Never a site, a domain or an address. Rate installed plugins and themes against known vulnerabilities in Settings → Security
wordpress.org’s directory: is a plugin closed? With each wpvulnerability.net lookup of a plugin, and of a theme it calls closed The slug of every installed plugin, custom ones included, and of a theme the feed calls closed As for wpvulnerability.net
wordpress.org: published checksums During malware scans, the first time a scan meets each WordPress or plugin version WordPress’s version and language. Each plugin’s folder name and version, custom ones included. Scan every site off in Settings → Security, with no site switched on by itself
Cloudflare, Jetpack, OpenAI, Anthropic, Google, Perplexity, Mistral and DuckDuckGo: published address lists Weekly, from the nightly housekeeping Nothing but the request None of its own. Pausing Nightly housekeeping stops it, and all pruning with it.
RIPE NCC, ARIN, APNIC, LACNIC and AFRINIC: tables of which country holds which addresses Weekly, from the nightly housekeeping Nothing but the request. Every country lookup happens on your server. As for the address lists
Your DNS resolver: crawler checks When an address that claims to be a search engine’s crawler crosses a detection rule That visitor’s address, as a reverse DNS lookup Automatic blocking set to Off
Google’s mail server, on port 25 Direct delivery only, at most every 5 minutes while the Mail page or the API asks for the relays’ status A connection, closed at once. No message. A smarthost: the check does not run then.
Request When What it sends Switch
wordpress.org’s plugin directory You search it, or add a plugin from it Your search words, or the plugin’s slug Only when you use it
Cloudflare’s API With a Cloudflare token: checking it, site records, going live through Cloudflare, mail records, wildcard certificates. Each server’s Traefik also uses it for the wildcard certificate’s DNS check. The token, zone and record names, and record values such as a server’s address Remove the token
Your DNS resolver Mail checks, going live, moving a site The names and addresses being checked Only when you use them
The nameservers of each domain a mail check looks up Mail checks: the Setup guide, DKIM & DMARC, and the Mail page’s reverse DNS The names being checked Only when you use them
The old site of an import While an import pulls it, and once to tell its plugin to stop when you disconnect or delete the import Signed requests for the list of its files, their contents and its tables’ rows Disconnect on the site page, or Delete import
A site hosted elsewhere Its address every minute, its plugin every hour, and for every scan, update, backup, command and login A request for its home page. Signed requests to WPL7 Connect, with what each one asks for: updates, files and rows for a backup, a command’s arguments. Disconnect on the site’s Settings tab

Send feedback on the About page sends nothing from the panel. A bug report or a feature request opens on GitHub in your browser, under your own account. A question or an idea opens the community’s forum, wpl7.com/community, in a new tab with your text filled in. Your browser sends what you typed there, with the build and machine details while Include what this install is is on. Nothing is public until you post it.

The panel hands its own mail to your relay, like your sites do:

  • Alerts go to Send alerts to in Settings, then Monitoring: a site’s mail suspended, malware found or moved, failing offsite copies, a catalog zip that matches known malware, a new release, and PHP security releases. With their switches on, also a site down or back up, a new vulnerability, a failed backup, and a site hosted elsewhere whose plugin stops answering or whose certificate expires soon. Leave the address empty to only log them.
  • Account mail goes to an account’s recovery address, or to a new one being confirmed, and only when someone asks: a password reset link, a confirmation link, and the notice that a password changed.

The panel connects to every server you add over SSH. It asks every running site for its home page for the uptime check, and a new domain for its home page when the site goes live. Offsite copies go to the destinations you add.

The installer and every update download the release from GitHub. Servers pull container images from GitHub’s container registry and from Docker Hub, and packages from Ubuntu’s mirrors and Docker’s repository. A server pulls the scanner image for its first scan, rclone for its first offsite copy, the FTP server image for its first FTP login, and Adminer the first time a database opens in it. Adminer’s own check for new versions is turned off.

  • Certificates: Traefik asks Let’s Encrypt for each certificate, naming its domains, and gives the ACME_EMAIL address for the account. Certificates are published in public Certificate Transparency logs, so every name with a certificate of its own becomes public. A wildcard certificate shows only the wildcard.
  • Traefik’s version check: Traefik asks update.traefik.io now and then whether it is out of date, and sends its version and the server’s public address. WPL7 does not switch it off.
  • Mail: the relays deliver what your sites send, to the recipients’ mail servers or to your smarthost.

Sites reach the internet, and the panel does not filter what they send. WordPress checks wordpress.org for updates and downloads from it, and plugins and themes call their own services. The inventory scan and the WordPress cron the panel runs both let WordPress check for updates. A recipe activates a pro plugin’s license through the plugin’s own code, so the plugin contacts its vendor to activate the key for the site’s address. Switching on a site’s object cache downloads the Redis Object Cache plugin from wordpress.org.

A site hosted elsewhere calls the panel too. WPL7 Connect sends the panel its report once, when it connects. It downloads its own updates, and plugins from the panel’s catalog, from links the panel signed for it.

In your browser, the panel loads everything from your own panel. When you search the wordpress.org directory, your browser loads the plugins’ icons from wordpress.org.

  • The published address lists and the country tables have no switch of their own.
  • Traefik’s version check has no switch in the panel.
  • Ubuntu itself, such as its package updates, is outside this list.