After resize getting ERR_CONNECTION_TIMED_OUT error

Hi there,

It sounds like your web service might not be up and running after the restart.

Can you share a bit more information of your current setup?

For example if you are using Apache, I would recommend following the steps here on how to troubleshoot common Apache problems:

https://www.digitalocean.com/community/questions/how-to-troubleshoot-common-apache-issues-on-linux-server

Mainly try restarting the service and checking the logs as described in the post above.

If you are using Nginx, follow the steps here:

https://www.digitalocean.com/community/questions/how-to-troubleshoot-common-nginx-issues-on-linux-server

If your application is running inside a Docker container instead, check to see if the container is actually running with docker ps -a and restart it with docker restart <container_id> if it is not running.

Feel free to share more details about your exact setup and I will be happy to advise you furhter.

Best,

Bobby

Heya, @dmohanty

Bobby might be just right that there are two firewall configurations. It’s good that you’ve quickly found the culprit and fixed the issue. You can check if there is an active Cloud Firewall to ensure if the issue comes from there.

If you want to decide which tool to use you can keep in mind that Cloud Firewalls comes handy when you want the same rules on multiple droplet.s

UFW is a host-based tool. That is, it has to be configured on each Droplet separately and add the necessary rules manually.

https://www.digitalocean.com/community/tutorials/how-to-set-up-a-firewall-with-ufw-on-ubuntu

DigitalOcean’s Cloud Firewall is a network-based one. The same firewall rules can be applied on a large number of Droplets. DigitalOcean’s Cloud Firewall has the advantage of scalability. As it supports tagging of the Droplets, we can add custom labels to Droplets.

Regards