Unable to Connect to Database via pgAdmin4 when connected to VPN

Context Users may encounter the following error while attempting to connect to a PostgreSQL database through pgAdmin4 while connected to a VPN: [Errno 8] nodename nor servname provided, or not known This issue can occur across multiple database environments when hostname resolution fails while connected to the VPN. Answer This error typically indicates that the client system is unable to resolve the database hostname. A common cause is an outdated or misconfigured VPN client that fails to handle internal DNS resolution correctly. When this happens, pgAdmin4 cannot resolve internal database endpoints, even though the database and DNS are functioning normally. To resolve the issue: Update the VPN client to the latest version. For OpenVPN users, upgrade to version 3.8.1 or later . Older versions may not properly route DNS queries for internal hosts. Reconnect to the VPN using a valid configuration. Go to DuploCloud Portal --> Profile. Re-import the latest VPN configuration using the credentials. Reconnect to establish a new session. Verify DNS Resolution Run nslookup to confirm the hostname resolves successfully. Once confirmed, retry connecting to the database from pgAdmin4.