A visitor gets "403 Forbidden" on a /.jsop-challenge/ address and cannot open a protected site
Why visitors flagged by the address check were refused the "just checking" page on a site behind the bot filter, and how to confirm and fix it.
On a site that has the scraper-bot filter switched on, some visitors see 403 Forbidden from nginx at an address like /.jsop-challenge/?to=/mod/quiz/view.php?id=980 and cannot open anything. Everyone else opens the site normally. The nginx error log for the domain shows access forbidden by rule for the same address.
What it means
The visitor check marks an address it does not trust and sends that visitor to a short "just checking" page, so they can show they are a person. On a site behind the bot filter, that page was refused before it could open. The result is that the visitors the check distrusts most, which includes many people sharing one school or office address, could open nothing at all. Visitors the check did not flag never saw it, which is why it can look fine from your own connection.
This was found from a log and from the site's own settings file. The 8 October 2026 build adds the missing exemption for the check page. It is built to open the page for those visitors, and it has not yet been confirmed on a server by an upgrade.
Steps
- Confirm it is this problem. On the server, replace
DOMAINwith the site:sudo grep 'jsop-challenge' /var/log/nginx/DOMAIN-error.log | tail -5
Lines endingaccess forbidden by ruleon a/.jsop-challenge/address mean yes. - Upgrade the server to the build dated 8 October 2026 or later:
sudo jsopctl upgrade
- Open the site from a visitor the check had flagged, or ask the affected person to try again. The "just checking" page should open and then let them through.
sudo jsopctl anubis domain ACCOUNT DOMAIN off, then on.