Website disabled by the security system
Why a website is suspended when it starts Chrome, FFmpeg or another executable.
Your website stopped responding (for example with 503 – Service Unavailable or a disabled application pool) and you received a message that it was disabled by our automated security system. This happens when the application starts a separate program on the server.
Why it happens
The security system watches which programs websites start. Launching a third-party executable from a website is how malicious code usually behaves, and some tools put an extreme load on a shared server. When such a process is detected, the website is suspended automatically.
Typical triggers:
| What the application started | Free | Premium |
|---|---|---|
| Chrome or Edge (Puppeteer, Playwright, Selenium) | Not allowed | Allowed |
| FFmpeg | Not allowed | Allowed for short jobs |
| Other executables (for example a bundled Python runtime or a custom tool) | Reviewed case by case | Reviewed case by case |
| Windows Defender or another antivirus scanner | Not allowed | Not allowed |
What to do
Open a support ticket
Tell us which website it is and what the program is used for. If it is a legitimate part of your application, we enable the website again and, where possible, add an exception for it.
Remove the call on the Free plan
If the tool is not allowed on your plan, remove that functionality from the application or upgrade to Premium.
Note
Even on Premium, an application should not run demanding or long-running processes continuously. Short jobs — extracting a few video frames, creating a PDF — are fine.
Scanning uploaded files for viruses
Our servers run antivirus protection with a real-time scanner, but it is a server-level service: your application cannot call it or ask it to scan a file. To scan files uploaded by your users, call an external scanning service over HTTPS from your application, for example VirusTotal, OPSWAT MetaDefender Cloud, Cloudmersive or Scanii.