After resize getting ERR_CONNECTION_TIMED_OUT error

I just did a resize of my droplet and everything seems smoothly, using CentOS 9 Stream x64, LEMP but unable to know why website is down.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Site Moderator
Site Moderator badge
April 22, 2024

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.

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.


Bobby Iliev
Site Moderator
Site Moderator badge
April 17, 2024

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:

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

If you are using Nginx, follow the steps here:

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.



Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel