- Branding works slowly.
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.
Following errors could be found in error log for Branding on the Management Node:
# tail -1 /var/www/vhosts/cp.example.com/logs/error_log [error] [client 192.168.0.1] proxy: DNS lookup failure for: cp.example.com returned by /
where cp.example.com is the branding domain name.
The branding domain is not resolved or resolved to incorrect IP on the management node.
- Go to the management node by SSH.
Check if the branding domain is resoved properly:
# nslookup cp.example.com
The branding domain must be resolved to correct IP address which belongs to the management node. If it is not, perform the following checks:
Make sure that the DNS A-record for the domain cp.example.com is resolved to correct IP address from outside:
# nslookup cp.example.com 220.127.116.11
- Check if there are correct DNS servers in
/etc/resolv.confon the management node
Try to resolve any external domain from the management node:
# nslookup odin.com
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:
192.168.0.1 is the IP address to which branding domain is resolved.