Article ID: 124983, created on Mar 23, 2015, last review on Feb 15, 2016

  • Applies to:
  • Plesk Automation 11.5

Symptoms

The provisioning task fails with the error:

The unexpected HTTP code '400'

Adding the IP address of the Node in binding of any website causes the error:

Invalid Hostname. 

When adding this IP address to binding, I got the following error:

Binding information 'IP:80:' is unsupported with dynamic mode. The Windows Process Activation Service (WAS) restart is required to register that binding.

Cause

The behavior was considered as internal software issue #PPA-2327. The latest Windows updates break IIS bindings.

The fix is included in Plesk Automation MU#21.

Resolution

Install latest PA updates according to the article.

Search Words

The unexpected HTTP code '400' was received on the HTTP request to the agent at

Internal error during processing statistic

The request hostname is invalid

The unexpected HTTP code '400'

code 400

Binding information is unsupported with dynamic mode. The Windows Process Activation Service (WAS) restart is required to register that binding.

33a70544d00d562bbc5b17762c4ed2b3 caea8340e2d186a540518d08602aa065 e0aff7830fa22f92062ee4db78133079

Email subscription for changes to this article
Save as PDF