Port 80 is closed on my machine.
It is not iptables...
It is not a port forwarding issue on my network.
Sentora "knows" the port is closed in the Service Status section.
I never really noticed this as everything on this server is using Let'sEncrypt / Certbot certificates.
I am left to assume it could be in my port override(s) or something I did. I seem to recall having to screw with the port 80 entry (because I am running CentOS 7) when setting up for Let'sEncrypt long ago. Does anyone have any quick advice on tracking this down?
I thought I would post first as I work on it so if I am not successful in figuring this out. This is sort of my fault as I was lazy in installing Zabbix and used the repo instead of installing it from source - thinking updates would be easier, but this also means zabbix is not in the sentora hostdata directory as a site. I don't think that matters, but if I would have done it that way, I would have secured it with SSL too and not have an issue with needing port 80.
I am stumped since SENTORA "knows" the port is closed...
Cheers @TGates if you are out there, I'm back! Thanks in advance.
It is not iptables...
It is not a port forwarding issue on my network.
Sentora "knows" the port is closed in the Service Status section.
I never really noticed this as everything on this server is using Let'sEncrypt / Certbot certificates.
I am left to assume it could be in my port override(s) or something I did. I seem to recall having to screw with the port 80 entry (because I am running CentOS 7) when setting up for Let'sEncrypt long ago. Does anyone have any quick advice on tracking this down?
I thought I would post first as I work on it so if I am not successful in figuring this out. This is sort of my fault as I was lazy in installing Zabbix and used the repo instead of installing it from source - thinking updates would be easier, but this also means zabbix is not in the sentora hostdata directory as a site. I don't think that matters, but if I would have done it that way, I would have secured it with SSL too and not have an issue with needing port 80.
I am stumped since SENTORA "knows" the port is closed...
Cheers @TGates if you are out there, I'm back! Thanks in advance.
Everyone makes mistakes, but to truly screw up it takes the root password!