Skip to main content

ClamAV® is disabled for this account

William Persico
  • Updated

Symptoms

If a ClamAV scan gets stuck or when executing the start_scan API for a user it returns the following:

# uapi --user=bobby ClamScanner start_scan scan_type='mail';
apiversion: 3
func: start_scan
module: ClamScanner
result:
  data: ~
  errors:
    - ClamAV® is disabled for this account.
  messages: ~
  metadata: {}

  status: 0
  warnings: ~

 

Description 

This is caused because the cPanel account has either not been configured or configured to have all the scan disabled.

 

Examples:

The user bigdog has not been configured:

Screenshot_2021-04-22_at_07.53.10.png

bigdog's user Settings:

Screenshot_2021-04-22_at_07.53.25.png

 

Workaround

You can add the user in question to the Configured Users list by selecting the user in the User List and pressing the "add" button. This will apply the default values you have configured to the user:

Screenshot_2021-04-22_at_07.57.43.png

 

An alternative solution is to configure the user individually by searching for the user in the text field under the ClamAV Scanner User Configuration section:

Screenshot_2021-04-22_at_07.58.04.png

Related articles