Debugging Connectivity Issues

Learn how to test and resolve connectivity issues affecting your Pantheon sites.


Connectivity Error Message

The following indicates that there was a networking error when attempting to connect:

Command:    open "dev.b098f987-asf7-47af-d0a9s-po7s987f342497@appserver.dev.b098f987-asf7-47af-d0a9s-po7s987f342497.drush.in" 2222
Error:  ssh_init: Host not found
Error:  Could not connect to server''
Debugging connectivity issues

Services such as MySQL and SFTP are running; however, the local client is unable to connect due to an idled container or DNS issues. Before further troubleshooting, wake the environment by loading the home page or via the following Terminus command:

terminus env:wake <site>.<env>

Resolve DNS Issues

Some ISPs have issues resolving a drush.in hostname. Troubleshoot connection errors using the following dig command, replacing <xxx> with your site’s UUID:

dig codeserver.dev.<xxx>.drush.in +short

If there is no IP provided in the output, the default DNS server used for the query (typically configured by your ISP) has failed to recognize the hostname. Run the query again with an alternate DNS server specified, such as one of Google’s Public DNS IP Addresses:

dig @8.8.8.8 dig codeserver.dev.<xxx>.drush.in +short
192.317.200.218

If an IP address is returned, configure your network settings to use Google Public DNS.

Port 2222 or Other Blocked Ports

Make sure the port number is not blocked by your internal firewall. For example, to test whether port 2222 is blocked visit http://portquiz.net:2222/

Test Connection on the Command Line

We recommend using the command line when troubleshooting connection issues as GUIs can hide underlying errors. From the site Dashboard, copy the provided connection command for the desired service and run it in terminal.