Searching for how to install SafeLine WAF on Debian raises two separate questions: whether your server meets the documented requirements, and how you will move application traffic through the firewall. The supplied installation guide specifies Linux, but it does not provide a Debian release compatibility list or Debian-specific package instructions. Treat this article as a deployment decision checklist, with the official guide as the reference for installation details.
Check the host before scheduling installation
Start by recording the Debian release, processor architecture, available resources, and installed container tooling. SafeLine’s official deployment guide lists Linux, x86_64 or arm64, Docker 20.10.14 or later, Docker Compose 2.0.0 or later, and minimum resources of one CPU core, 1 GB memory, and 5 GB disk. It also lists an ssse3 CPU requirement. These are documented minimums; they do not establish capacity for your application’s workload. Source: installation guide
The guide supplies inspection commands including uname -m, docker version, docker compose version, free -h, and df -h. Use their output to identify prerequisites that need attention before deployment. For Debian package installation or Docker repository configuration, obtain appropriate instructions separately; those procedures are not established by the supplied SafeLine documents. Source: installation guide
Architecture also affects the deployment decision. The guide states that ARM installations require a Pro license and that the Personal Edition does not support ARM. Confirm this before committing an ARM host to the project. Source: installation guide
Choose an installation path you can review
The official guide recommends automatic deployment and states that its installer requires root privileges. It also documents a manual Docker Compose deployment. Decide which procedure fits your administration practices before scheduling the work. Source: installation guide
For the manual route, prepare a persistent directory and review the supplied Compose environment settings. The documented example uses /data/safeline, defines a database initialization password, and sets the management console port to 9443. Keep a record of the directory and configuration choices so another administrator can understand the deployment. Source: installation guide
For a new deployment, also review the release selection. The guide states that LTS maintenance ended beginning with version 9.1.0-LTS, dated August 14, 2025, and recommends upgrading LTS installations to the latest version. Source: installation guide
Map the application traffic before changing DNS
SafeLine operates as an HTTP/HTTPS reverse proxy: it receives requests for the website and forwards permitted traffic to the original application. This makes the intended traffic path a central part of installation planning. Source: application configuration guide
Write down three values for your first application: its public domain, the port SafeLine should listen on, and the upstream address of the existing application. These correspond to the documented Add Application fields. The guide also instructs administrators to select the SSL option for HTTPS applications. Source: application configuration guide
As an operational precaution, check whether another service already uses your intended listening ports. Record the current DNS destination and a restoration procedure before making changes. The documented configuration sequence ends by resolving the application domain to the SafeLine server’s IP address, so that DNS change deserves its own review point. Source: application configuration guide
Define what a successful rollout means
Use separate acceptance checks for administration and application traffic. The installation guide describes accessing the console at https://<safeline-ip>:9443/ and obtaining administrator credentials with docker exec safeline-mgt resetadmin. Successful console access confirms that you can administer the instance. Source: installation guide
Then verify normal application behavior through the intended domain. As a practical checklist, cover login, navigation, uploads, and API requests relevant to your service. Perform any security validation only against applications you control or have permission to test. The application guide provides example attack requests and explains how to inspect blocked requests and their details in the console. Source: application configuration guide
Does the documentation explicitly confirm support for my Debian release?
No Debian release matrix appears in the supplied sources. The installation guide specifies Linux and the listed architecture, software, and resource requirements. Meeting those requirements is a starting point for evaluation, not a documented Debian-version guarantee. Source: installation guide
Can I use an ARM Debian server?
The guide lists arm64, requires ARCH_SUFFIX=-arm for manual ARM deployment, and states that ARM requires a Pro license. It does not establish compatibility with a particular Debian release. Source: installation guide
Does installing SafeLine automatically protect my website?
The documented workflow also requires adding the application, defining its listening port and upstream, and resolving its domain to the SafeLine server. Include those configuration steps in your rollout plan. Source: application configuration guide
What should I verify after changing DNS?
Check that normal application requests succeed through the intended route, then inspect the console during authorized security testing. The official guide describes an attack list and a detail view for investigating blocked requests. Source: application configuration guide
Ready to turn this checklist into a deployment plan? Explore the official SafeLine project and follow the official documentation.