Job Clerk Blog

NHS Jobs help

NHS Jobs 403 error: what Request blocked means and how to troubleshoot

Understand an NHS Jobs 403 or CloudFront Request blocked message, try a few safe checks, and gather the right details for support.

By Job Clerk · · 5 min read

An NHS Jobs page showing “403 ERROR”, “Request blocked” or “The request could not be satisfied” means the request was refused. If the page mentions CloudFront, the message comes through Amazon’s content-delivery service. It does not tell you whether your application was saved, whether your account is locked, or whether other applicants have the same problem.

What a CloudFront 403 can tell you

Amazon’s CloudFront documentation lists several possible reasons for a 403, including firewall rules, geographic restrictions and configuration or access rules at the underlying server. The same status code can come from different parts of the service.

The wording alone does not identify which reason applies to NHS Jobs. Only the service operator can investigate its configuration and logs. A 403 is therefore not proof that NHS Jobs is down worldwide, that your account has been banned, or that your password is wrong.

Our NHS Jobs status page separates blocked access from other errors and missing observations. It reflects our tested routes. Your browser may work while our checks are blocked, or your connection may fail when a listing check succeeds.

Try these checks in order

  1. Protect your work. Copy any unsaved application text into a private document before refreshing, signing out or changing browser settings. A blocked request does not confirm whether your latest changes reached the service.
  2. Start at the official website. Open NHS Jobs and navigate to search or applicant sign-in. Avoid entering account details into a site claiming it can “unblock” NHS Jobs for you.
  3. Check official service information. Read NHSBSA’s maintenance information, including the date and time. Do not treat a past notice as the explanation for today’s error.
  4. Compare a fresh browser session. After saving your text, try a private window or another up-to-date browser. This helps compare sessions; it is not a guaranteed fix. Do not clear all stored browser data as your first step.
  5. Compare a trusted connection. If permitted, try your own mobile connection instead of workplace Wi-Fi. If you use an optional personal VPN, try without it. Follow workplace IT rules and leave required security controls in place.
  6. Stop if the block persists. Record what happened and contact support. Repeated refreshes, rotating proxies or paid “unblocking” services are not useful applicant troubleshooting steps.

These are diagnostic comparisons, not a way to bypass an access restriction. If a different browser works, that narrows the problem to the tested conditions; it does not prove that cookies caused it. If another connection works, it does not prove that NHS Jobs has blocked a whole country or organisation.

A blocked page and a login error need different help

If the normal sign-in form loads and rejects your credentials, use NHSBSA’s login instructions. They cover the applicant login page, password reset and account lockouts. If a CloudFront block appears before you reach that form, changing your password may not address the failed request.

Do not keep submitting passwords to test whether the site works. Return to the official sign-in page once it is reachable. When you get back in, check your application’s saved content and submission status rather than assuming the failed screen means it was lost or sent.

What to send to NHS Jobs support

Use NHSBSA’s official applicant support details. A short, specific report is easier to investigate than “the site is broken”. Include:

  • The affected public page or vacancy reference and the action you attempted.
  • The date and time, stating UK time or your time zone.
  • The exact error wording and HTTP code, if shown.
  • Your browser and device, whether you were on home, work or mobile internet, and which comparisons you tried.
  • A redacted screenshot and any CloudFront request ID shown, shared privately with official support.

Do not send passwords, session cookies, reset links or an unredacted application screenshot. Remove private tokens from page addresses before sharing them. You do not need to publish your IP address or application details to report an access problem.

If the error is blocking a time-sensitive application

Contact the recruiting employer using the advert’s details and explain the error and deadline. Ask how to proceed; neither Job Clerk nor a 403 message can grant an extension or confirm that another submission route is accepted. Our guide to checking NHS Jobs access covers protecting your draft and handling an approaching closing date.