• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved Port 80 closed?!

LMAR6

New Pleskian
Hi!

I'im installing a new server and got a strange problem. The hosting accounts are not reachable due the closed port 80.

1) Why is this port closed? It's just Cloudlinux 7.3 + Plesk Onyx 17.0.17 Update Nr. 15 , nothing changed during installation...

2) I can't open Port 80.
  • disabled included firewall from webhoster
  • plesk firewall app: WWW server Allow incoming from all
  • iptables: ACCEPT tcp -- anywhere anywhere tcp dpt:http
What else could be blocking port 80? How can I debug this?

Ports tested with dnstools.ch and Nmap.

Thanks in advance.
 
Hi Peter!

Code:
# netstat -plnt | grep ':80'
no output
Code:
# netstat -plant | grep ':80'
no output
Code:
# netstat -plant | grep 'LISTEN'
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 1075/dovecot
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 1075/dovecot
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 1075/dovecot
tcp 0 0 0.0.0.0:8880 0.0.0.0:* LISTEN 1304/sw-cp-server:
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 1415/master
tcp 0 0 xx.xx.xx.xx:53 0.0.0.0:* LISTEN 1316/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 1316/named
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 3416/sshd
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 1415/master
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 1316/named
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 1304/sw-cp-server:
tcp 0 0 0.0.0.0:4190 0.0.0.0:* LISTEN 1075/dovecot
tcp 0 0 127.0.0.1:12768 0.0.0.0:* LISTEN 844/psa-pc-remote
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 1075/dovecot
tcp6 0 0 :::995 :::* LISTEN 1075/dovecot
tcp6 0 0 :::7080 :::* LISTEN 3414/httpd
tcp6 0 0 :::7081 :::* LISTEN 3414/httpd
tcp6 0 0 127.0.0.1:3306 :::* LISTEN 1313/mysqld
tcp6 0 0 :::106 :::* LISTEN 839/xinetd
tcp6 0 0 :::110 :::* LISTEN 1075/dovecot
tcp6 0 0 :::143 :::* LISTEN 1075/dovecot
tcp6 0 0 :::8880 :::* LISTEN 1304/sw-cp-server:
tcp6 0 0 :::465 :::* LISTEN 1415/master
tcp6 0 0 :::53 :::* LISTEN 1316/named
tcp6 0 0 :::21 :::* LISTEN 839/xinetd
tcp6 0 0 :::22 :::* LISTEN 3416/sshd
tcp6 0 0 :::25 :::* LISTEN 1415/master
tcp6 0 0 :::8443 :::* LISTEN 1304/sw-cp-server:
tcp6 0 0 :::4190 :::* LISTEN 1075/dovecot
tcp6 0 0 :::993 :::* LISTEN 1075/dovecot

I hope this helps!
 
You are using Nginx as reverse proxy. Your ports 7080 and 7081 are active, they are the upstream ports of Nginx->Apache. But The default Nginx web server ports are not active. Probably Nginx is not running or misconfigured.

Can you please check whether Nginx is running?
# service nginx status

If it is not running, please start it by
# service nginx start
 
Thank you! I should have known that...Problem solved :)

The restart of nginx worked. I will now check the reason for the failed start after the last reboot. But I think, I can do this on my own ;)
 
Back
Top