apache server not found after droplet resize.

Heya, @momentumindiaprivatelimited

You can check if the Apache configuration files and virtual hosts are still present. It might be a case where the Apache server was not properly started after the resize.

You can use the following command to check the status of Apache:

sudo systemctl status apache2

If Apache is not running, start it:

sudo systemctl start apache2

If you are using a package manager like npm or Yarn to manage your Node.js dependencies, you need to update the package manager after resizing your droplet in order to get the latest versions of your dependencies.

We strongly recommend taking a snapshot of the Droplet before resizing.

Droplets may change hypervisors during a resize, and any changes to a filesystem can lead to data loss if something goes wrong. We strongly recommend backing up the Droplet’s data before resizing. If you use snapshots, you can delete the snapshot after confirming that the resize was successful.

https://docs.digitalocean.com/products/droplets/how-to/resize/#considerations-before-resizing

Regards

Heya,

That’s really weird as resizing shouldn’t be affecting software like that. Do you by any chance have any backups prior to the resize which you can use?

As for the Apache service, can you try reinstalling it with:

apt install apache2

What does it say? It should be something like:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
apache2 is already the newest version (2.4.54-2ubuntu1.3).

Additionally, can you find apache in /etc/apache2?