How can I troubleshoot the issue when attempting to add a PostgreSQL Database server, but encountering a failure with an error message prompt?
While attempting to add a PostgreSQL database monitor, if you encounter any errors, please follow the steps below based on the specific error received:

Host not valid. Kindly check the host name given
or

PostgreSQL production server is down
or

The host could not be reached. Check whether you are able to connect to the host with the details given
Issue: The errors occur when Applications Manager is unable to connect to the PostgreSQL server. This could be due to a hostname resolution issue or a firewall restriction.
Solutions:
- Check Network Connectivity
- Open command prompt on the Applications Manager installed server.
- Attempt to ping the PostgreSQL server using the following command:
ping <postgresql_hostnme> - Verify if there is a successful response indicating network connectivity.
- Hostname Lookup
- In the command prompt, verify if the hostname of the PostgreSQL server can be looked up using following command:
nslookup <postgresql_hostname> - Ensure that the hostname can be resolved to an IP address.
- Check Firewall Settings
- Verify if there are any firewall restrictions blocking the connection to the PostgreSQL server.
- Ensure that the necessary ports (e.g., default port 5432 for PostgreSQL) are not blocked by the firewall.

Could not add the PostgreSQL server. Check whether the server is running on the specified
host: postgresql_hostnme and port: 5432.
Kindly check your firewall configurations and user credentials.
Issue: The error happens when Applications Manager can't connect to the PostgreSQL server port. This might be because of a wrong port setting, firewall restrictions preventing access, or not having permission to connect to the PostgreSQL port from the Applications Manager server.
Solutions:
- Check Port Connectivity
- Open a command prompt on the Applications Manager installed server.
- Test port access to the PostgreSQL server by running the following command:
telnet <postgresql_hostnme> <port> - Monitor the command response to see if a blank screen appears, indicating successful port connectivity.
- If you receive an error like "Could not open connection to the host, on port 5432: Connect failed", you need to verify the PostgreSQL port / network connectivity

Access denied for remote servers.Change configurations in pg_hba.conf and postgresql.conf file
or

Authentication failed.Kindly verify the configurations in your pg_hba.conf file and the user credentials given.
or

Connection to the PostgreSQL server unsuccessful as password authentication failed for user.
Issue: The error occurs due to restrictions in the PostgreSQL Configuration (pg_hba.conf and postgresql.conf files) preventing remote access to the PostgreSQL server from Applications Manager.
Solutions:
- Open a command prompt on the Applications Manager installed server and navigate to the "AppManager\working\pgsql\bin" directory in the command prompt.
Execute the following command:
psql --host=<postgresql_hostname> --port=<port> --username=<username> <dbname>
For example:
psql --host=192.168.100.101 --port=5432 --username=postgres postgres
- Based on the response or error message received from the above command, verify the username and password credentials if necessary. Then, take appropriate steps to further diagnose and resolve the issue before making changes to the pg_hba.conf and postgresql.conf files to ensure that the remote access issue is effectively resolved.
- If the issue persists even after attempting the above steps, kindly share the output of the above command with the error message to appmanager-support@manageengine.com to analyze this further.
New to ADSelfService Plus?
Related Articles
Troubleshooting Bad Request and Internal Server error
When a server responds with a Bad Request (400) or Internal Server Error (500), It typically indicates issues with how the request is being made or processed. The reasons for these errors can vary, but the most common causes are Incorrectly formatted ...
Error message while performing database backup of Applications Manager
While performing a database backup operation of Applications Manager build with Pgsql backend, you may encounter the following error, especially when your database size has grown bigger with a large number of tables. pg_dump: WARNING: out of shared ...
Mail Server Monitor - Troubleshooting
Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...
Oracle Database Server Discovery Fails with an Error Message
Error: Failed. Oracle Server is down. Error Message: IO Error: The Network Adapter could not establish the connection Solution 1: The Oracle server is down, please ensure that the server is up and running. Solution 2: The Oracle server is not ...
How to fix "Communication link failure The last packet sent successfully to the server"?
Issue: Communication link failure error message will trigger based on many reasons. Solution: Communication link failure error message is shown due to various reasons. Follow any of the steps mentioned below to resolve the issue: Insufficient user ...