# Verbindungsfehler nach dem Ändern der Größe eines DO Droplet

**URL:** <https://meta.discourse.org/t/connection-error-after-resizing-do-droplet/78596>\
**Category:** Self-hosting\
**Created:** [21. Januar 2018 um 18:22 UTC](https://meta.discourse.org/t/connection-error-after-resizing-do-droplet/78596 "2018-01-21T18:22:01Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![tkrunning](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tkrunning/32/119481_2.png) [@tkrunning](https://meta.discourse.org/u/tkrunning)\
**Post date:** [22. Januar 2018 um 07:47 UTC](https://meta.discourse.org/t/connection-error-after-resizing-do-droplet/78596/4 "2018-01-22T07:47:54Z")

</div>

Yup, looks like apache was listening.

```
root@community:~# netstat -plnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1318/sshd       
tcp6 0 0 :::80 :::* LISTEN 1478/apache2    
tcp6 0 0 :::22 :::* LISTEN 1318/sshd       

```

For future reference (or to help other noobs), I ran `sudo apache2ctl stop`, then `./discourse-setup` like @pfaffman suggested to reconfigure for the new amount of RAM. At the end of that process discourse was rebuilt and my site is back up!

I’m not sure if this was necessary, but finally I ran `sudo systemctl disable apache2` to make sure apache does not run when my droplet is restarted in the future. ([Source](https://askubuntu.com/questions/170640/how-to-disable-apache2-server-from-auto-starting-on-boot))

Thanks a lot guys!

---

_[View the full topic](https://meta.discourse.org/t/connection-error-after-resizing-do-droplet/78596)._