I installed Hestia with nginx only setup. But a test web site does not respond (ERR_TIMED_OUT). Nginx service is running and no error in logs. What else I should check? Any extra step after install for nginx only setup?
You should check:
1.- That the domain you are using points to your server’s public ip.
2.- Check that you have a rule in your firewall allowing connections to ports 80 and 443.
v-list-firewall
3.- Check that you are not banned from your own server:
v-list-firewall-ban
Firewall or ban system is not enabled… And pinging domain responds to server ip. I install Debian 12. Should I go back Debian 11?
Are you sure?
iptables -S
nft list table filter
If you share the domain we can test it from our side.
Yes it did not even installed them.
v-update-firewall
Error: FIREWALL_SYSTEM is not enabled
service fail2ban stop
Failed to stop fail2ban.service: Unit fail2ban.service not loaded.
Domain is ns2ip.com
You don’t have a service listening on port 80, only on port 443.
lsof -Pn +c0 -i:80,443 -sTCP:LISTEN
Check nginx conf:
nginx -t
And check the nginx conf for your site:
cat /home/*/conf/web/ns2ip.com/nginx.conf
cat /home/*/conf/web/ns2ip.com/nginx.ssl.conf
lsof -Pn +c0 -i:80,443 -sTCP:LISTEN
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
nginx 17113 root 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17113 root 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17114 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17114 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17115 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17115 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17116 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17116 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17117 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17117 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17118 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17118 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17119 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17119 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17120 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17120 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17121 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17121 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17122 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17122 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17124 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17124 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17125 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17125 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17126 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17126 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17127 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17127 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17128 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17128 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17129 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17129 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx 17130 www-data 12u IPv4 71027 0t0 TCP 95.216.246.48:80 (LISTEN)
nginx 17130 www-data 13u IPv4 71028 0t0 TCP 95.216.246.48:443 (LISTEN)
nginx.conf files also has:
server {
listen 95.216.246.48:80;
Then something is blocking port 80, check if you have activated Hetzner firewall.
I confirmed that they are not blocking it. So this could be something with Debian. Should I reinstall 11/12 ?
I can provide you root access if you want to take a look?
I would try to figure out what’s going on before reinstalling but if you want to reinstall use Debian 12 again.
I’ll contact you via private message.
My bad… It was a Nat port forwarding issue for an other vm at proxmox that was blocking port 80.
Thanks again.