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)
Thanks a lot guys!