Search Engine: Elastic

Article ID: 122020, created on Jun 13, 2014, last review on Jul 21, 2015

  • Applies to:
  • Plesk Automation 11.5


  1. Branding works slowly.
  2. When trying to login to PA by using branding URL, the following error is displayed:

    Bad Gateway
    Web server received an invalid response while acting as a gateway or proxy server.
  3. Following errors could be found in error log for Branding on the Management Node:

    # tail -1 /var/www/vhosts/
    [error] [client] proxy: DNS lookup failure for: returned by /

    where is the branding domain name.


The branding domain is not resolved or resolved to incorrect IP on the management node.


  1. Go to the management node by SSH.
  2. Check if the branding domain is resoved properly:

    # nslookup

The branding domain must be resolved to correct IP address which belongs to the management node. If it is not, perform the following checks:

  1. Make sure that the DNS A-record for the domain is resolved to correct IP address from outside:

    # nslookup
  2. Check if there are correct DNS servers in /etc/resolv.conf on the management node
  3. Try to resolve any external domain from the management node:

    # nslookup

If external domains can not be resolved from the management node, check DNS, firewall and network settings on the management node. After all DNS issues are resolved the access through the branding URL will start working properly.

As a temporary workaround the following record can be added /etc/hosts on the management node:

where is the IP address to which branding domain is resolved.

33a70544d00d562bbc5b17762c4ed2b3 e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF