Searching for “how to install SafeLine WAF on CentOS” raises two separate questions: does your server meet the documented requirements, and how will website traffic reach the firewall? Answering both before deployment gives you a clearer path from an available machine to a working application proxy.
The supplied SafeLine installation guide specifies Linux, but it does not identify supported CentOS releases or provide CentOS-specific package instructions. Treat this article as a deployment readiness checklist based on the official documentation, rather than confirmation that a particular CentOS version is supported. Official installation guide
Start with a host readiness decision
The documented minimum requirements are Linux, an x86_64 or arm64 architecture, Docker 20.10.14 or later, Docker Compose 2.0.0 or later, one CPU core, 1 GB of memory, and 5 GB of disk space. The requirements table also lists the ssse3 CPU instruction. ARM deployment has an additional qualification: the guide states that it requires a Pro license and that Personal Edition is not supported on ARM. Requirements and architecture notes
For an existing CentOS machine, record the installed operating system release, architecture, container tooling versions, available resources, and current workloads before deciding to proceed. The official guide supplies these inspection commands:
uname -m
docker version
docker compose version
free -h
df -h
lscpu | grep ssse3
These checks establish facts about the host; they do not establish CentOS release compatibility. If Docker or Compose is missing or below the documented minimum, resolve that prerequisite before attempting the SafeLine deployment. Avoid substituting an assumed CentOS package recipe for instructions that the supplied sources do not contain.
Write down the traffic path first
SafeLine operates as an HTTP/HTTPS reverse proxy: it receives requests for the website and forwards accepted traffic to the original application. Installing the software is therefore only part of the deployment. Official application configuration guide
Prepare a short worksheet with the application domain, the port SafeLine should listen on, and the real upstream address of the application. Those are the fields identified in the official application setup procedure. For HTTPS applications, the guide instructs users to select the SSL option. It then directs users to resolve the configured domain to the server running SafeLine. Application fields and domain routing
Before changing domain resolution, record the existing destination and decide how you would restore it if application checks fail. Also identify representative application journeys to verify afterward, such as signing in, submitting a form, and opening a normal content page. These are operational planning recommendations, rather than additional SafeLine features.
Separate deployment from application onboarding
The official installation guide recommends automated deployment and states that the process requires root privileges. It also documents a manual deployment path using Docker Compose. Use the current official instructions as the execution reference once your host prerequisites are resolved. Deployment procedures
For manual deployment, the documented directory is /data/safeline, where SafeLine stores configuration and data. The guide provides a Compose file and environment settings, then starts the service with docker compose up -d. These are general deployment instructions; the supplied page does not add CentOS-specific service, firewall, or SELinux steps. Manual installation
After deployment, the documented console address is https://<safeline-ip>:9443/. The guide uses docker exec safeline-mgt resetadmin to obtain administrator credentials. Once logged in, application onboarding takes place through Applications → Add Application. Console access and application configuration are separate milestones, so verify each before changing production routing. Console access · Application onboarding
FAQ
Does the official guide confirm support for my CentOS release?
The supplied guide lists Linux as the operating system requirement without a CentOS release matrix. It therefore does not establish compatibility for your specific release. Use its prerequisites as an initial checklist and resolve distribution-specific questions before deployment. Installation requirements
Is reaching the management console enough to finish setup?
No. The application guide also requires configuring the domain, listening port, and upstream, followed by resolving the domain to the SafeLine server. Reaching the console confirms only one part of the documented workflow. Application setup
How can I check the deployment after routing traffic?
First verify that normal application journeys work. For a website you own or are authorized to test, the official guide also provides example attack requests and describes checking the blocking page and attack details in the console. Documented validation examples
Can I use the same checklist for an ARM server?
Include the architecture-specific conditions. The manual guide specifies ARCH_SUFFIX=-arm and states that ARM requires a Pro license. Do not assume that meeting the hardware minimums alone satisfies every deployment requirement. ARM deployment notes
Use this checklist to prepare your deployment, then explore the official project and follow the current documentation: SafeLine GitHub and official docs.