How to turn website protection on or off for one site

For hosting customers · Updated 2026-10-29

On this page
  1. Steps
  2. Good to know
  3. Common questions

Every website is protected by default: password guessers are blocked, attacks are stopped by the firewall, scripts cannot run from upload folders and security headers are sent. If an application really needs it, you can turn a protection off for one site.

Steps

  1. Log in to the control panel (https://<server>:2083).
  2. Open Access Control (section Domains).
  3. Scroll to Protection. Each website is listed with its switches:
    • firewall on / firewall off — the web application firewall
    • upload folders protected / upload folders not protected — scripts are not run from uploads folders
    • security headers on / security headers off
    • HTTPS enforced in browsers / HTTPS not enforced in browsers — shown only when the site has a certificate
  4. Click Turn off or Turn on next to the protection.

The change is applied within a minute.

Good to know

  • Turn a protection off only for the site that needs it, and turn it on again when you no longer need it.
  • HTTPS enforcement cannot be undone quickly: browsers then refuse to open the site without HTTPS for a year, even if the certificate is removed. You are asked to confirm.
  • The list under Protection shows recent attacks on your sites: time, website, address and what was stopped.
  • Whether the firewall refuses attacks is set by your hosting provider for the whole server. When it is only recording, attacks are listed but not stopped.
  • Blocking a visitor yourself: use the IP block list higher up on the same page.

Common questions

My form or plugin gets a "403 Forbidden" error. Is this the firewall?

It can be, if the request looks like an attack (for example code or SQL in a form field sent in the address). Check the list under Protection for that website at that time. If it is listed, turn the firewall off for that site, or ask the plugin's maker for a fix.

A script in my uploads folder does not run. Why?

upload folders protected stops .php files from running in folders named uploads or upload, because that is how hacked sites usually get a backdoor. Move the script to another folder, or turn the protection off for that site.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.