Article ID: 1658, created on Oct 6, 2008, last review on May 11, 2014

  • Applies to:
  • Plesk 11.5 for Linux


The DrWeb service returns the following startup error:

Plesk authorization failed: HTTP request error [6]
Error: Plesk Software not running.


The DrWeb package that comes with the Parallels Plesk Panel (PP) distributive is configured to work with the PP CP and cannot be run standalone. It searches the PP CP on localhost:8443 for authorization and if this attempt fails, the error listed above occurs.


Make sure that the PP CP is running on port 8443 and that you are able to establish a connection to it:

#telnet localhost 8443  
Connected to localhost.localdomain (  
Escape character is '^]'.  

If you get the error from the command above, the reason may be as follows:

  • The localhost cannot be resolved or is resolved incorrectly. Make sure that the localhost entry exists in /etc/hosts. localhost localhost.localdomain    
  • If you see a "connection refused" error, try to start PP and make sure that there is no firewall running on the server blocking port 8443.

  • Also check that PP is configured to run on the 8443 port. The Listen 8443 directive must be in $PRODUCT_ROOT_D/admin/conf/httpsd.conf.

  • Check that you are able to log in to the PP CP in the usual way via your browser.

  • Finally, make sure that PP is responding to the DrWeb request by running the following command on the PP server and verifying the following response:

    # curl -d "challenge=123&checker=drweb" https://localhost:8443/check-plesk.php -k

In case you got no response, please verify that your License includes Dr.Web.

Search Words

Plesk authorization failed: malformed response (no 'response=' field).

29d1e90fd304f01e6420fbe60f66f838 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 01bc4c8cf5b7f01f815a7ada004154a2 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF