Could not connect to Server

Posted February 22, 2018 3.1k views
ApacheArch Linux

I cant connect to my server from today, yesterday it was working, please help me very very soon, i really need help on this. i can login to digital ocean dashboard, but through putty, ssh, filezilla and website are not working, please help me


These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

Hello, @testuser

It will be the best to perform a traceroute test to your droplet/server and see if you’re able to reach your server or see where the connection is being dropped.

See the instructions bellow for Mac, Windows and Linux:

Note that in our examples you will need to replace with your actual domain name.

For Windows 7 and older:

Open Start menu -> Click Run -> Type cmd and press Enter.

In the command prompt type tracert and press Enter.

For Windows 8.x and newer:

Use the search window, type command prompt and click on the Command Prompt result.



and press Enter.

This will provide traceroute results from your computer to You can also use tracert with an IP, i.e. tracert

For more information on how to copy and paste the traceroute results, please check this article.

Mac OS
You need to open up Terminal, located under Applications -> Utilities -> Terminal and type:


and press Enter.

Alternatively, you can go to the Applications folder -> Utilities -> Network Utility -> Traceroute and specify your domain or IP address.

You can also use traceroute with an IP, i.e. traceroute

Open a Terminal window and type:

traceroute -I

The -I option is necessary so that the traceroute uses ICMP. You can also use traceroute with an IP, i.e.

traceroute -I

You can also contact our support team and provide them with the result of the traceroute command and they will check this for you.

It will be good to test the connectivity from multiple locations using different broadband connection (if possible) in order to check if the issue is related with your ISP.

Hope this helps!