Skip to content

Cookie settings

Choose which kinds of cookies you allow. You can change your choice at any time via Cookie settings at the bottom of every page. Privacy statement

Necessary

Always on

Needed to log in, keep your cart and remember your choices. These are always on.

Which cookies?
  • weboke_sessie, weboke_klant, weboke_remember: your session and staying logged in
  • weboke_basket: your cart
  • wkBtwIncl: showing prices with or without VAT
  • wok_cookies: your cookie choice, 12 months

Measures which ad leads to a visit or order, so we do not pay for ads that do nothing.

Which cookies?
  • Google Ads via Google Tag Manager (_gcl_au, _gcl_aw), up to 90 days
  • OpenAI Ads, ads in ChatGPT
  • wok_aff: which partner referred you to us (affiliate programme), 60 days

4.6

Country and language

Each country has its own site, with prices and VAT for that country.

View

403 Forbidden caused by Imunify360 or the firewall

Do you click Update in WordPress, submit a form or upload a file, and get 403 Forbidden, 406 Not Acceptable or a blank page? Then a security measure is usually blocking the request because it looks like an attack. All our servers run the Web Application Firewall (ModSecurity) and Imunify360.

How to recognise it

  • The 403 or 406 only appears when you save, submit or upload, not when you simply view a page.
  • The error log of your domain contains a line with ModSecurity: Access denied with code 403 or IM360 WAF.

Other causes of a 403

  • A security plugin on your website, such as Wordfence, iThemes Security or All In One WP Security.
  • Wrong permissions: folders should be 755, files 644.
  • Hotlink Protection, if the 403 only appears for images.
  • A protected folder or a rule such as Deny from all in .htaccess.
  • A 403 on your entire website with You don't have permission to access / on this server: this usually means there is no index.php or index.html in public_html. See Forbidden (403): You don't have permission to access / on this server.

How to fix it

  1. Write down the time when it went wrong.
  2. In DirectAdmin, open Web Application Firewall and click Audit log next to your domain. Look for the request around that time: it shows the number of the rule that blocked it.
    The Audit log of the Web Application Firewall in DirectAdmin with the filter for domain, client IP or request line
    The audit log: which requests the firewall blocked
  3. Disable only that rule for this domain (see Web Application Firewall). Don't switch off the firewall completely.
  4. Do you use a security plugin? Check that plugin's logs, or disable it temporarily to test.

Please note: Do your website, email and DirectAdmin not load at all from your own internet connection, but do they work over 4G? Then it isn't a 403 but an IP block. See Time-out: website, mail and FTP suddenly unreachable.

When should you contact us?

Is it a message from Imunify360 (IM360 WAF), or can't you find the rule? Send us the line from the error log and the address of the page, and we'll take a look.

Ask the AI assistant in My WebOké first, or create a ticket via Support centre and then Submit a ticket. Include:

  • the full address of the page where it goes wrong
  • the time when it went wrong
  • what you were doing at that moment, for example saving, uploading or logging in
  • a screenshot of the message
  • the line from the error log with ModSecurity or IM360 WAF

Never send your password.

More detail: Error 403 or 406 when saving or uploading and Imunify360: scanning your website for malware.

One moment…

Set up your domains

For each domain, arrange the nameservers, the link to your hosting and who becomes the owner.

Loading your domains…