Cannot enable inbound HTTP traffic to my droplet

Posted March 16, 2020 2.3k views


Recently I attached a new domain to my droplet (currently there are two attached). Since then, I cannot reach my droplet through HTTP requests on port 80, the result is always 404 not found.

I tried everything: rules in iptables, setup a firewall in digital ocean UI with enabling rule for HTTP/S.

I tried with nginx, python SimpleHTTPServer module, none of them are reachable.

I cannot tell if the problem arose due to my new domain or not (which BTW has A, CNAME and NS entries), but the SSH(22), K3S(6443) and TCP(8000) ports work, the latter two after I added a rule for them in iptables and firewall.

Probably there’s something wrong with my setup (and not DO’s fault), but this is getting really frustrating because it completely blocks me (cannot create new certificates, cannot test, etc.).

Does anyone have any idea what could have gone wrong?
The system inside the droplet is Ubuntu 18.04.1LTS,
Linux 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x8664 x8664 x86_64 GNU/Linux.

Thank you!

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.

Submit an Answer
1 answer

Hi @popescuaf,

The 404 error is related to your website’s vhost configuration rather than your firewall. If you couldn’t open your website via port 80 or 443 you’ve get a connection refused error rather than 404.

Having said that, please make sure to check your vhost configuration and configure it properly. Depending on the WebService you are using, either Nginx or Apache, you can check the following articles how to configure a vhost file

Apache -

Nginx -


by Justin Ellingwood
When using the Nginx web server, server blocks (similar to the virtual hosts in Apache) can be used to encapsulate configuration details and host more than one domain off of a single server. In this guide, we'll discuss how to configure server blocks in Nginx on an Ubuntu 16.04 server.
  • Hi KDSys,

    Thanks for your answer. It is indeed not a firewall problem, seems to be related to k3s. The iptables rules are changed after installing it and I think the 80 port is taken over by the internal load balancer of the k3s service. I rebuilt the droplet from scratch, tried port 80 (worked), then installed k3s, then tried again port 80 (didn’t work anymore). So I guess I’ll have to figure it out myself.

    Thank you for your support!