SafeLine operates as a reverse proxy, similar to Nginx. It intercepts incoming web traffic, filters and analyzes it, and then forwards the legitimate traffic to your original web server.
Configuration Steps
Environment Information:
-
Web Server: IP Address A (IPA), External Port 80, Domain:
example.com. For this example, IPA is192.168.117.6. - SafeLine Server: IP Address B (IPB).
Steps:
-
Redirect Web Traffic: Point your original web traffic to SafeLine's IPB. This is a mandatory step. For example, modify your domain’s DNS settings to direct
example.comto IPB. - Configure SafeLine: Refer to the configuration settings in the image provided.
- Restrict Access: Block all direct access to your web server except for traffic coming from SafeLine. This can be done by configuring your firewall.
Once you've completed the setup, your configuration should look something like this:
Testing the Setup
After pointing example.com:80 to SafeLine, try accessing the site in your browser. If you receive a response from your web server, it means traffic is successfully passing through SafeLine.
Now, go back to SafeLine's dashboard and check the "Today's Requests" section in the data statistics page.
If you see the number of requests increase, it confirms that SafeLine is successfully handling your web traffic.
Advanced Protection
The latest version of SafeLine now includes advanced protection features for individual sites, allowing you to apply additional security settings per site.
Note: Custom rules are not affected by the current toggle status.
Human Verification
Enable human verification for individual sites by clicking the relevant option.
Authentication
You can also set up an additional authentication rule for specific sites by clicking the authentication option.
Top comments (2)
How does Safeline compare to Cloudflare?
Great question! SafeLine and Cloudflare both offer robust web security solutions, but they serve different needs. I’d recommend trying it to see how it fits your needs: waf.chaitin.com.