Some visitors see "403 Forbidden" instead of a page that says "just checking"
What to do when you or your visitors get a plain 403 Forbidden error on an address that contains jsop-challenge.
You or some of your visitors see a plain white 403 Forbidden page, with the word nginx under it, and the address in the browser contains jsop-challenge. Other visitors open the site normally.
What it means
Your hosting provider's server can ask a visitor it does not trust to prove they are a person, using a short "just checking" page. That page was being refused on sites that have the bot filter switched on, so the visitor saw a plain error and could not carry on. It is not a problem with your site or your files.
It tends to affect people who share one internet address with many others, such as a school or an office, because one noisy person can make the whole address look untrustworthy.
Steps
- Reload the page once. If it still shows the error, try from a different connection, such as a phone on mobile data, to confirm it is only affecting some visitors.
- Tell your hosting provider that visitors get
403 Forbiddenon an address containingjsop-challenge, and give them the site's name. They can fix it from their side.