Issue Can't access Updates and Upgrades. Port 8447 appears to be closed. Can't open.

[chakotha]

Hi

I have seen some similar questions online but I can't fix this.

I am trying to install PHP 7.4 so I can upgrade on our sites.

Updates & Upgrades goes to an Unable to connect time out page.

Googling suggests that port 8447 is closed needs to be opened. Strange because I used this method to install PHP 7.3 around 2 years ago without any issue and we have not changed anything as far as I know.

So I went into Plesk Firewall and created a rule to Allow Incoming to port 8447, but it doesn't appear to be working.

 

[chakotha]

Hi

I have seen some similar questions online but I can't fix this.

I am trying to install PHP 7.4 so I can upgrade on our sites.

Updates & Upgrades goes to an Unable to connect time out page.

Googling suggests that port 8447 is closed needs to be opened. Strange because I used this method to install PHP 7.3 around 2 years ago without any issue and we have not changed anything as far as I know.

So I went into Plesk Firewall and created a rule to Allow Incoming to port 8447, but it doesn't appear to be work

Hi

I have seen some similar questions online but I can't fix this.

I am trying to install PHP 7.4 so I can upgrade on our sites.

Updates & Upgrades goes to an Unable to connect time out page.

Googling suggests that port 8447 is closed needs to be opened. Strange because I used this method to install PHP 7.3 around 2 years ago without any issue and we have not changed anything as far as I know.

So I went into Plesk Firewall and created a rule to Allow Incoming to port 8447, but it doesn't appear to be working.

From remotely 8447 shows as filtered:

$ nmap -p 8443 ourdomain.com
...
PORT STATE SERVICE
8443/tcp open https-alt
...
$ nmap -p 8447 ourdomain.com
...
PORT STATE SERVICE
8447/tcp filtered unknown
...


On the server iptables seems to show it as open

$ iptables -S
...
-A INPUT -p tcp -m tcp --dport 8447 -j ACCEPT
-A INPUT -p udp -m udp --dport 8447 -j ACCEPT
...


But netstat doesn't list it among the open ports.

$ netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 2269/sw-cp-serverd
tcp 0 0 100.200.300.400:443 0.0.0.0:* LISTEN 752/nginx
tcp 0 0 0.0.0.0:4190 0.0.0.0:* LISTEN 641/dovecot
tcp 0 0 127.0.0.1:12768 0.0.0.0:* LISTEN 588/psa-pc-remote
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 641/dovecot
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 641/dovecot
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 922/mysqld
tcp 0 0 0.0.0.0:106 0.0.0.0:* LISTEN 770/xinetd
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 1398/master
tcp 0 0 0.0.0.0:32747 0.0.0.0:* LISTEN 1168/sshd
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 641/dovecot
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 641/dovecot
tcp 0 0 0.0.0.0:8880 0.0.0.0:* LISTEN 2269/sw-cp-serverd
tcp 0 0 100.200.300.400:80 0.0.0.0:* LISTEN 752/nginx
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 1398/master
tcp 0 0 172.17.0.1:53 0.0.0.0:* LISTEN 598/named
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 770/xinetd
tcp 0 0 100.200.300.400:53 0.0.0.0:* LISTEN 598/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 598/named
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 1398/master
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 598/named
tcp 0 0 127.0.0.1:12346 0.0.0.0:* LISTEN 1398/master
tcp6 0 0 :::8443 :::* LISTEN 2269/sw-cp-serverd
tcp6 0 0 2001:41d0:404:200:::443 :::* LISTEN 752/nginx
tcp6 0 0 :::7080 :::* LISTEN 978/apache2
tcp6 0 0 :::7081 :::* LISTEN 978/apache2
tcp6 0 0 :::587 :::* LISTEN 1398/master
tcp6 0 0 :::32747 :::* LISTEN 1168/sshd
tcp6 0 0 :::8880 :::* LISTEN 2269/sw-cp-serverd
tcp6 0 0 2001:41d0:404:200::1:80 :::* LISTEN 752/nginx
tcp6 0 0 :::465 :::* LISTEN 1398/master
tcp6 0 0 :::25 :::* LISTEN 1398/master


And netcat seems to say it is open

$ netcat -z -v 100.200.300.400 8000-9000
www.ourdomain.com [127.0.1.1] 8880 (?) open
www.ourdomain.com [127.0.1.1] 8447 (?) open
www.ourdomain.com [127.0.1.1] 8443 (?) open


But the Updates & Upgrades page is still not loading.

Any ideas? TIA

 

[Kaspar]

I am not sure about your port issue. However you could try to install php 7.4 via command line using the command:

# plesk installer add --components php7.4

 

[chakotha]

Thanks for responding.

If I run that command will it make PHP 7.4 available in each domain's Hosting Settings/PHP Settings so we can upgrade one site at a time.

Or will it put all our websites onto PHP 7.4 without our testing as we go?

I forgot to mention we are still on Debian 8.11. Might that cause the port issue? Updates and Upgrades did work before.

 

[Kaspar]

I forgot to mention we are still on Debian 8.11. Might that cause the port issue? Updates and Upgrades did work before.

Could be, I am not sure. Note that Debian 8 as been EOL for a long time now and is no longer supported, which should be a concern to you. I am also not sure if the Plesk php 7.4 component is actually available for Debian 8. (But maybe it is).

If I run that command will it make PHP 7.4 available in each domain's Hosting Settings/PHP Settings so we can upgrade one site at a time.

It will only install PHP 7.4 on your server so it becomes available for usage. You'll have to manually change the PHP version for each website (or change it in the service plan).

 

[Peter Debik]

@chakotha If you are using an EOL OS version, chances are Plesk cannot find the installation archives. Please see this post

Resolved - Plesk 18.0.44_3 repository error

Hi, I have a legacy server running Debian 9.13 with Plesk version18.0.44-3 (the last one available for the OS), and this morning I got this email: 2023-03-29 06:25:13 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2023-03-29 06:25:16 ERROR: E:The repository...

talk.plesk.com

for how to access older archives, but no guarantee yours will be included there. Debian 8, well, that ought to be the time to migrate to a Deb 11 now.

 

[KendalSmithy]

I have just posted a similar question to this but very soon found a quick workaround which doesn't involve messing with Port 8447 on our routers (although it does need to be open in the webserver itself). I enabled WiFi Hotspot Tethering on my mobile phone and connected my PC to the internet using mobile data. It seems port forwarding is not an problem by using this method. I was then able to open Plesk's Updates page without any problem.