Why is Apache 2 accessible from the public ip?

Community Support General Questions
1

After running ss -tlpn, I discovered that Apache2 is listening on publicIP:8080 and publicIP:8443.

However, all web server requests are routed through Nginx. So why does Apache2 need to be accessible via the public IP?

I would have expected apache2 to listen on 127.0.0.1:8080 and 127.0.0.1:8443

Update 2025:
The topic is closed now, but I wanted to mention that I have done a nmap from a different server and found out the port 8080 is open / You can recreate the issue by installing nmap
by sudo apt install nmap on ubuntu from a different server
Then do nmap yourhestiahostname
and check.
Meanwhile the port 8433 is nowhere to be seen and it is good news.

image
image1369×734 47 KB

Hestia CP does use either A standalone Nginx or Nginx + Apache in the backend.
I don’t see the point of using a public IP address in nginx.conf and apache configuration files.

I think it would be better for performance to use 127.0.0.1 instead of public IP.

2

The ports are blocked by iptables, they are not reachable from public.

1 Like
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.