The site does not open from the outside, port 80. Server apach2 + nginx (VestaCP) Which direction to dig?

Question

linux

The site does not open from the outside (port 80).
It all started after:
I tried to start nodejs-express and added port 3000 to the allowed list and forwarded port 3000 to 80 ( But then I removed the forwarding ).
I worked so-so and was happy with phantomjs, and suddenly I see that the site does not open through port 80.
Ports of a personal account and mysql work.
iptables --list:

Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:ssh
ACCEPT     tcp  --  anywhere             anywhere             multiport dports http,https
ACCEPT     tcp  --  anywhere             anywhere             multiport dports ftp,12000:12100
ACCEPT     udp  --  anywhere             anywhere             udp dpt:domain
ACCEPT     tcp  --  anywhere             anywhere             multiport dports smtp,ssmtp,submission,2525
ACCEPT     tcp  --  anywhere             anywhere             multiport dports pop3,pop3s
ACCEPT     tcp  --  anywhere             anywhere             multiport dports imap2,imaps
ACCEPT     tcp  --  anywhere             anywhere             multiport dports mysql,postgresql
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:8083
ACCEPT     icmp --  anywhere             anywhere
ACCEPT     all  --  debian               anywhere
ACCEPT     all  --  localhost            anywhere
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:ftp-data
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:ftp
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:ssh
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:smtp
ACCEPT     udp  --  anywhere             anywhere             udp spt:domain
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:http
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:https
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:pop3
ACCEPT     udp  --  anywhere             anywhere             udp spt:ntp
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:imap2
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:mysql
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:postgresql
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:http-alt
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:8433
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:8083
ACCEPT     tcp  --  anywhere             anywhere             tcp spts:12000:12100
ACCEPT     tcp  --  anywhere             anywhere             state RELATED,ESTABLISHED

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain fail2ban-MAIL (0 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

Chain fail2ban-SSH (0 references)
target     prot opt source               destination
REJECT     all  --  12.237.115.7         anywhere             reject-with icmp-port-unreachable
RETURN     all  --  anywhere             anywhere

Chain fail2ban-VESTA (0 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

Chain fail2ban-ssh (0 references)
target     prot opt source               destination
DROP       all  --  12.237.115.7         anywhere
RETURN     all  --  anywhere             anywhere

Chain vesta (0 references)
target     prot opt source               destination

Answer 1

Chain INPUT (policy DROP)
I think your packets are dropping :)
write
iptables -S you will see the rule
then write
iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
And you will open port 80.

Answer 2

And actually it is possible to receive a nginx config? There is generally a normal such option that, in principle, he listens to you lo

Answer 3

Thanks Azazel, iptables --policy INPUT ACCEPT helped. Now we need to solve the problem with nginx. But that's different, I've experienced this before.