stillorigin protects your website by stopping attacks, unwanted bots and other bad traffic. Now and then it may stop someone you do want to visit. This article explains how to work out why, and what to do about it.
What a blocked visitor sees
What your visitor sees depends on where the block happened.
The block page
Most blocks show a page titled "Request not accepted ยท stillorigin". It reads:
This request was not accepted
Reason: this request looked like an attack.
If you think this is a mistake, contact the website's owner or their host, and tell them when you saw this page.
At the bottom it says Protected by stillorigin.
The reason line changes with the kind of block (see Step 3 below). If the reason isn't known, there's no reason line at all.
No page at all
Some blocks happen on your host's network, before the request reaches your website's protection. The visitor doesn't see a page. Instead, your site just won't load for them, or it times out. This happens for:
- addresses your host blocks for all its sites, including addresses on the stillorigin naughty list
- connection and rate limits on your host's network
- country blocks and crawler blocks on your host's network
- services your host blocks for all its sites, such as some AI crawlers. On the Blocks tab these show as blocked: (service name). Contact your host if you want the service allowed.
- temporary blocks
It can also happen for secure (HTTPS) visits if your host passes HTTPS through to your website without inspecting it.
A browser check, not a block
If your visitor saw a page titled Checking your browser with an I'm a person tick box, they weren't blocked. That's Captcha Protection checking they're a real person. If they didn't get through, ask them to turn on JavaScript in their browser and try again. See "The browser check your visitors may see".
An error from your website
If your website itself sends an error, such as "page not found", the visitor sees your website's own error page. stillorigin never replaces it. On the Blocks tab it shows as Error response from your site (404) (or another number). It's counted with blocked requests, but your protection didn't block it. Check the page or link on your website instead.
Step 1: Get some details from your visitor
Ask your visitor for:
- Roughly when it happened (date, time and their time zone).
- The reason line on the page, if there was one, or whether the site just wouldn't load.
- Their IP address. They can find it by searching for "what is my IP" in any search engine.
- The page they were trying to open.
Step 2: Check the Blocks tab
- Open Manage protection from your hosting account (see "Signing in to your website protection").
- Click the Blocks tab.
- Look at Why requests were blocked for the reasons, and Most blocked IP addresses for your visitor's IP address.
Times in your protection area are shown in UTC, not your local time, so convert the time your visitor gave you.
Step 3: Match the reason and fix it
Find the reason line your visitor saw. Each one matches one or more reasons on your Blocks tab. They're listed alphabetically.
"Reason: automated visitors of this kind are not allowed."
On Blocks you'll see one of:
- AI crawler (bot blocking)
- Script or HTTP library (bot blocking)
- SEO crawler (bot blocking)
These come from Bot blocking on the Settings tab, which blocks bots by how they identify themselves. If you want that kind of bot, untick it under Bot blocking. Scripts and HTTP libraries can also block uptime monitors and other services that connect to your site.
If you don't see Bot blocking on Settings, your host manages it for you. Contact your host if you'd like it changed.
"Reason: this automated service is not allowed."
On Blocks you'll see one of:
- blocked by default: (service name): your host blocks this service by default. You can allow it on Settings, under Blocked by default by your host.
- blocked by owner: (service name): blocked under Block AI crawlers and other services on Settings. Untick it if you want that service.
- Fake crawler: something claimed to be a well-known service, such as a search engine, but didn't come from that service's official addresses. Your host manages this setting.
If you don't see Block AI crawlers and other services on Settings, your host manages it for you. Contact your host if you'd like it changed.
"Reason: this page is limited to allowed addresses."
On Blocks you'll see Admin login lock: address not allowed. Someone opened your WordPress login page or admin area from an address that isn't on your list.
If it was you or someone on your team, add their IP address under Allowed IP addresses in the Admin login lock section of Settings, then click Save addresses. See "Locking your WordPress login".
If you don't see Admin login lock on Settings, your host manages it for you. Contact your host if you'd like it changed.
"Reason: this request looked like an attack."
On Blocks you'll see one of:
- an attack check, such as Database attack (rule 942100)
- Folder escape attempt
- Internal WordPress file request
- Request for a private file
- Script run from uploads folder
- WordPress setup file request
- WordPress user listing attempt
- WordPress XML-RPC request
These are usually automated attacks, and you don't need to do anything. The WordPress protections are built in and always apply, and your host manages the attack checks. If a real visitor, or a plugin or tool you rely on, keeps getting caught, contact your host with the reason, the IP address and roughly when it happened.
"Reason: too many requests. Please try again shortly."
On Blocks you'll see Too many requests. One IP address sent more requests than the rate limit allows. This block is temporary, so ask the visitor to wait a few minutes and try again.
If it keeps happening to real visitors and your host lets you set your own rate limit, you can raise it under Rate limit on Settings. Otherwise, contact your host.
"Reason: visitors from this country are not allowed."
On Blocks you'll see Country rule: followed by the country's name.
If you added the country, change or remove it on the Countries tab. You can switch it to a Captcha Protection check instead of a block. Countries marked Blocked by your host can't be changed by you, so contact your host.
If you see "Your host manages country blocking for your site." on Countries, contact your host if you'd like it changed.
No reason line
If the page had no reason line, contact your host with the visitor's IP address, the page and roughly when it happened.
The site won't load and nothing shows on Blocks
If your visitor's browser just can't load your site, and there's nothing for their IP address on the Blocks tab, the block probably happened on your host's network. It could be an address your host blocks, or an address on the stillorigin naughty list. Blocks like these usually don't appear on your Blocks tab.
- Ask your visitor to check their address at https://stillorigin.app/check.
- If it's listed, they can ask for it to be removed (see below).
- If it's not listed, contact your host with the visitor's IP address and roughly when it happened.
The naughty list
The naughty list is a shared list of IP addresses that have recently been caught sending abusive traffic. Only use these steps if the naughty list is the actual cause. Removing an address from the list doesn't help with any of the reasons in Step 3.
On your Blocks tab, a naughty list block usually shows nothing. The exception is Browser check: naughty list, when your host asks naughty list addresses to complete a browser check instead of blocking them. In that case, the check page tells the visitor their address may be on the list, with a link to check it.
Check an address
Your visitor can check their address at https://stillorigin.app/check. To go straight to one address, add it to the end, for example https://stillorigin.app/check/1.2.3.4.
Remove an address
To ask for an address to be removed, the visitor goes to https://stillorigin.app/delist. The request:
- must come from the listed address itself, so the visitor needs to be on the same internet connection that was blocked
- is confirmed by email
How soon the address comes off depends on how often it's been listed in the last 90 days:
- First listing: straight after the visitor confirms.
- Second listing: 24 hours after the visitor confirms.
- Third listing or later: it needs a review by the stillorigin team, or comes off when the listing expires.
Blocks in log mode
While your Website protection rules are in log mode, attack checks only record what they would block and let those requests through. These still block, even in log mode (in alphabetical order):
- the admin login lock, if it's on
- Block AI crawlers and other services, and services your host blocks by default
- bot blocking
- country blocks you've set to Enforce
- rate limits (Too many requests)
- WordPress protections
So a visitor can still be blocked while your site is in log mode. See "Log mode and blocking".