PBAS cannot perform any operation related to external systems such as payment processing centers, domain registrars and/or SSL certificate vendors.
The error messages may be different for different operations (due to different plug-ins used).
Payment transactions may fail with an error: A communication error occurred while connecting to the server.
Domains registration/renewal through the eNom registrar may fail with an error:
Error occurred during renewal. Error: eNom communication level error: ApplicationError: Application error occurred, contact provider for details.
In general, errors say about communication problems.
PBAS cannot connect to the external system because it cannot resolve its hostname to IP address.
To make sure that the problem is related to DNS resolving perform the simplest test:
- Get hostname of the external system in PBAS PCC in domain or payment plug-in settings, e.g. it may be hostname of the eNom registrar reseller.enom.com or www.paypal.com for payments through PayPal.
- Log into PBAS server by SSH as root
- Get the IP address of name server from the /etc/resolv.conf file, let it be 192.168.1.101
- Try to resolve hostname of an external system you found on the step 1 using DNS server from the /etc/resolv.conf file using the dig utility:
# dig reseller.enom.com @192.168.1.101
Replace 192.168.1.101 in the command above with the actual IP address from the /etc/resolv.conf file on PBAS Management Node.
If you see error message and cannot resolve hostname to IP address it means DNS server used by PBAS malfunctions. As a result PBAS cannot resolve hostname of any external system and cannot connect to it to perform provisioning operation.
E.g. the error message may be as follows:
dig reseller.enom.com @192.168.1.101 ;; global options: printcmd ;; connection timed out; no servers could be reached
Fix the problem with DNS server configured in the /etc/resolv.conf file on PBAS server or put IP address of working server into the file.
Restart PBAS backend:
# service hspcd restart