Ports 80 and 443 blocked after droplet reboot

Hi there,

A few things worth checking before opening a support ticket.

First, verify nginx is actually binding correctly after the reboot:

sudo ss -tlnp | grep -E '80|443'
sudo systemctl status nginx

Sometimes nginx fails to start cleanly after a reboot due to a certificate issue or config error, even if a previous systemctl status looked fine.

Check your DigitalOcean cloud firewall. If your Droplet is assigned to one, those rules are applied at the network level and survive reboots independently of anything on the Droplet itself. Go to Networking > Firewalls in the control panel and confirm ports 80 and 443 are allowed inbound.

Then check ufw or iptables on the Droplet itself:

sudo ufw status
sudo iptables -L INPUT -n

A reboot can sometimes cause ufw to come up in a state that blocks traffic even if your rules look correct.

Keitaro also has its own internal firewall config worth checking after an unexpected reboot.

If all of the above looks clean and ports are still blocked externally, open a support ticket at https://cloud.digitalocean.com/support and ask them to check for any network-level restrictions on that Droplet. Include the IP and region as you have here, that will speed things up.

Heya, @glebfox

Check the DO cloud firewall rules in the control panel specifically - sometimes after a reboot the firewall config doesn’t match what you expect even if ufw/iptables looks fine locally. Two separate layers.

Also run sudo nginx -t and check sudo systemctl status nginx just to confirm it survived the reboot cleanly.

But realistically if ports are blocked at the network level and SSH is fine, that’s on DO’s side and only support can lift it. Make sure your ticket mentions the unexpected reboot, the timing, and that nginx is confirmed running and listening - gives them the context to investigate faster.

Regards