The Firewall, Cloudflare and Activity sections of the Security tab decide who may reach your site and show you what was stopped. As everywhere on the tab, press Apply to site to make changes live.
Firewall
The firewall refuses requests that look like SQL injection, script injection, file-inclusion tricks, probes for secret files (such as .env, .git and wp-config.php) and well-known hacking tools. It looks at the address of the request and the browser name, not at the contents of forms you submit. Visitors who are signed in and addresses on your allow list are never checked.
Block addresses, and always allow yours
- Block these addresses: up to 300 entries, one per line. Use a single address or a range such as
198.51.100.0/24. - Always allow these addresses: up to 100 entries. Your office or home address goes here. It is never blocked, challenged or locked out by anything on this tab.
Single IPv4 addresses and /8, /16 and /24 ranges are refused by the web server itself, so even pages served from the page cache are covered. Other ranges and IPv6 addresses are refused on every page that runs WordPress.
Block countries
Pick the countries to block. Visitors from them see an "access denied" page. The country of an address comes from the free IP geolocation data of DB-IP.com, which FlyNode downloads for your site and refreshes by itself. A visitor whose country cannot be told is let in. Two things to know:
- While the country block is on, the page cache is switched off for your site so that every visit is checked, so the site may be a little slower.
- Do not block the country you work from. If you do, change it back from the Security tab (your dashboard is not affected).
Stop bot floods with Cloudflare
When thousands of bots hit your site, the best defence works before the traffic reaches your server. Cloudflare does that for free: it sits in front of your site, and only the traffic it lets through arrives. The Cloudflare section of the Security tab shows the steps:
- Add your domain to Cloudflare (free plan) and change the nameservers at your registrar to the two Cloudflare gives you.
- Point the domain at your site and turn the cloud orange. In Cloudflare's DNS page, the A records for your domain and
wwwuse the address shown on your app's Custom Domain tab. Click the grey cloud so it is orange (Proxied). - Set SSL/TLS to Full (strict). If you see a redirect loop, this setting fixes it.
- Turn on Bot Fight Mode under Security. During an attack, set the Security Level to I'm Under Attack! and set it back to Medium afterwards.
- Block attackers in Cloudflare with a custom WAF rule on their addresses.
Use one CDN only: if you use QUIC.cloud's CDN, turn it off for this domain first and keep the LiteSpeed Cache plugin. Behind Cloudflare, FlyNode sees Cloudflare's addresses and not your visitors', so block visitors in Cloudflare, and never block Cloudflare's own addresses.
Activity log
The Activity section lists sign-ins and everything the protection stopped, for the last 30 days: wrong passwords, lock-outs, wrong two-factor codes, firewall blocks, blocked addresses and countries, and visits to the old login address. Repeats from one address within a minute are shown on one line with a count. Press Block on a line to add that address to the block list. Use the filter to show one kind of event, and the switch Keep the activity log to stop recording.
The activity log records addresses of visitors who tried to sign in or were blocked. Only keep it on if that suits your privacy policy.
Still stuck?
Open a support ticket from your dashboard and include the container name.