• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue Connectivity issues in Ubuntu Server 22.04

I

ItsPerona

Basic Pleskian
Server operating system version
Ubuntu 22.04.5
Plesk version and microupdate number
18.0.65.2
Hi, after an apt-upgrade I did a reboot, and now I can't access my server via FTP or SSH, it seems that I have no internet connection.
I was about to upgrade to Ubuntu 24 since it appears as recommended by my provider, and it also appears that Plesk for my version of Ubuntu Server is unsuported.

After doing the Reboot I can no longer access the server via FTP or SSH, it seems that the server cannot ping the outside.

Bash: 
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:25:90:46:6d:87 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:25:90:46:6d:86 brd ff:ff:ff:ff:ff:ff
    altname enp3s0
    inet 85.214.113.41/32 metric 100 scope global dynamic eno1
       valid_lft 82454sec preferred_lft 82454sec
    inet6 fe80::225:90ff:fe46:6d86/64 scope link
       valid_lft forever preferred_lft forever

Bash: 
# /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search stratoserver.net
 
Raul A. said:
Please share the output of
Code: 
ip ro sh
Click to expand...

Code: 
default via 85.214.64.1 dev eno1 proto dhcp src 85.214.113.41 metric 100
81.169.163.106 via 85.214.64.1 dev eno1 proto dhcp src 85.214.113.41 metric 100
85.214.7.22 via 85.214.64.1 dev eno1 proto dhcp src 85.214.113.41 metric 100
85.214.64.1 dev eno1 proto dhcp scope link src 85.214.113.41 metric 100
212.227.123.16 via 85.214.64.1 dev eno1 proto dhcp src 85.214.113.41 metric 100
212.227.123.17 via 85.214.64.1 dev eno1 proto dhcp src 85.214.113.41 metric 100
 
That is good. You have a default gateway, obtained via DHCP.

Next let's check the firewall.

Bash: 
iptables -S INPUT
And
iptables -S OUTPUT

Also try setting a nameserver in /etc/resolve.conf. try at the begining of the file:
Code: 
nameserver 1.1.1.1
 
Raul A. said:
That is good. You have a default gateway, obtained via DHCP.

Next let's check the firewall.

Bash: 
iptables -S INPUT
And
iptables -S OUTPUT

Also try setting a nameserver in /etc/resolve.conf. try at the begining of the file:
Code: 
nameserver 1.1.1.1
Click to expand...


Code: 
~# iptables -S INPUT
-P INPUT DROP
-A INPUT -p tcp -m tcp --dport 22 -j f2b-ssh
-A INPUT -p tcp -m multiport --dports 25,465,587 -j f2b-plesk-postfix

~# iptables -S OUTPUT
-P OUTPUT ACCEPT
I need to execute something else after change /etc/resolve.conf?
 
Bash: 
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 1.1.1.1
nameserver 127.0.0.53
options edns0 trust-ad
search stratoserver.net
 
You have no actual rules in the INPUT chaind and the policy is DROP.

Change the policy and enable the firewall from Plesk

Bash: 
iptables -P INPUT ACCEPT
 
I have connected and been able to upgrade to Ubuntu 24.04 but I have 2 problems.

1. Every time I reboot I have to use "iptables -P INPUT ACCEPT" again
2. Plesk doesn't seem to work anymore, using plesk login, plesk repair etc does nothing
 
Solution to problem 1 is to enable the firewall from Plesk.

For problem 2, is plesk atually installed and running?
Bash: 
systemctl status sw-cp-server sw-engine
Can you access the database service?
Bash: 
plesk db
 
Raul A. said:
Solution to problem 1 is to enable the firewall from Plesk.

For problem 2, is plesk atually installed and running?
Bash: 
systemctl status sw-cp-server sw-engine
Can you access the database service?
Bash: 
plesk db
Click to expand...



Bash: 
~# systemctl status apache2
× apache2.service - The Apache HTTP Server
     Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Fri 2025-01-03 23:19:06 CET; 24min ago
       Docs: https://httpd.apache.org/docs/2.4/
        CPU: 354ms

ene 03 23:18:47 h2946496.stratoserver.net systemd[1]: Starting apache2.service - The Apache HTTP Server...
ene 03 23:19:06 h2946496.stratoserver.net apachectl[1810]: AH00112: Warning: DocumentRoot [/usr/share/plesk-service.localdomain] does not exist
ene 03 23:19:06 h2946496.stratoserver.net apachectl[1810]: AH00112: Warning: DocumentRoot [/usr/share/plesk-service.localdomain] does not exist
ene 03 23:19:06 h2946496.stratoserver.net apachectl[1810]: AH00526: Syntax error on line 15 of /etc/apache2/plesk.conf.d/webmails/iperona.com_webmail.conf:
ene 03 23:19:06 h2946496.stratoserver.net apachectl[1810]: SuexecUserGroup configured, but suEXEC is disabled: Missing suexec binary /usr/lib/apache2/suexec
ene 03 23:19:06 h2946496.stratoserver.net apachectl[1767]: Action 'start' failed.
ene 03 23:19:06 h2946496.stratoserver.net apachectl[1767]: The Apache error log may have more information.
ene 03 23:19:06 h2946496.stratoserver.net systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
ene 03 23:19:06 h2946496.stratoserver.net systemd[1]: apache2.service: Failed with result 'exit-code'.
ene 03 23:19:06 h2946496.stratoserver.net systemd[1]: Failed to start apache2.service - The Apache HTTP Server.


~# systemctl start apache2
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xeu apache2.service" for details.


~# plesk db
-bash: /usr/sbin/plesk: No existe el archivo o el directorio


~# systemctl status sw-cp-server sw-engine
Unit sw-engine.service could not be found.
● sw-cp-server.service - Startup script for Plesk control panel server
     Loaded: loaded (/usr/lib/systemd/system/sw-cp-server.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/sw-cp-server.service.d
             └─respawn.conf
     Active: active (running) since Fri 2025-01-03 23:18:46 CET; 24min ago
   Main PID: 1754 (sw-cp-serverd)
      Tasks: 2 (limit: 38333)
     Memory: 7.1M ()
        CPU: 64ms
     CGroup: /system.slice/sw-cp-server.service
             ├─1754 "sw-cp-server: master process /usr/sbin/sw-cp-serverd -c /etc/sw-cp-server/config"
             └─1755 "sw-cp-server: worker process"

ene 03 23:18:42 h2946496.stratoserver.net systemd[1]: Starting sw-cp-server.service - Startup script for Plesk control panel server...
ene 03 23:18:46 h2946496.stratoserver.net systemd[1]: Started sw-cp-server.service - Startup script for Plesk control panel server.
 
Try to install Plesk again How to Install Plesk On Linux?
Code: 
Installing Plesk via CLI

    Download Plesk installer: wget https://autoinstall.plesk.com/plesk-installer
    Add proper permissions to Plesk installer: chmod +x plesk-installer
    Run Plesk installer via command line and follow instructions: ./plesk-installer or ./plesk-installer --all-versions
    First you will need to confirm your decision by choosing “Go forward” and in case of –all-versions there will be option to choose the certain version of Plesk
    Wait until installation process is done
 
Bash: 
~#  sh <(curl https://autoinstall.plesk.com/one-click-installer || wget -O - https://autoinstall.plesk.com/one-click-installer)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 16190  100 16190    0     0   104k      0 --:--:-- --:--:-- --:--:--  105k
You can't use one-click-installer since you already have Plesk installed.
You should use interactive installer mode instead, to use it run 'plesk installer' in shell console.
Note: to run Plesk installer using Web UI (https://<you_host>:8447) you should use --web-interface option, in other cases it will work via shell console.

~# plesk installer
plesk: orden no encontrada
I dont understand what is happening
 
Please try the other approach, not the one-click-installer.

Data should still be on the server. Just some Plesk components were removed during apt actions.
 
Bash: 
:~# ./plesk-installer --web-interface
--2025-01-04 00:10:34--  http://autoinstall.plesk.com/Installer/3.46.0/parallels_installer_Ubuntu_24.04_x86_64
Resolviendo autoinstall.plesk.com (autoinstall.plesk.com)... 84.17.61.32, 185.152.65.27, 84.17.61.36, ...
Conectando con autoinstall.plesk.com (autoinstall.plesk.com)[84.17.61.32]:80... conectado.
Petición HTTP enviada, esperando respuesta... 404 Not Found
2025-01-04 00:10:36 ERROR 404: Not Found.--2025-01-04 00:10:36--  http://autoinstall.plesk.com/Parallels_Installer/parallels_installer_Ubuntu_24.04_x86_64
Resolviendo autoinstall.plesk.com (autoinstall.plesk.com)... 185.152.65.27, 84.17.61.32, 84.17.61.36, ...
Conectando con autoinstall.plesk.com (autoinstall.plesk.com)[185.152.65.27]:80... conectado.
Petición HTTP enviada, esperando respuesta... 404 Not Found
2025-01-04 00:10:36 ERROR 404: Not Found.
ERROR: You are trying to run Plesk Installer on an unsupported OS.
Your OS is Ubuntu 24.04 x86_64
The list of supported OS is at https://docs.plesk.com/release-notes/current/software-requirements/

Is this the other approach? :(
 
This was the other approach.

You get
> ERROR: You are trying to run Plesk Installer on an unsupported OS.

Because of the HTTP 404 earlier in the script output. Ubuntu 24.04 is properly detected.

That appears to be an old plesk-inataller.

Download the ubuntu 24.04 package from this page : Index of /Installer/3.66.0
 
You must log in or register to reply here.

Similar threads

C
Issue Correct IPV6 Traffic Routing
Replies
0
Views
1K
Change Maker
C
Quinten
Issue Cannot remove local IP
Replies
4
Views
2K
Quinten
Quinten
C
Resolved IPv6 not working
Replies
2
Views
2K
Creativados
C
VojinP
Resolved Problem with assigning IPv6 to new server
Replies
4
Views
3K
VojinP
VojinP
LorisMod
Resolved Problems with additional IPv4 not working
Replies
5
Views
4K
mostaqim
M
Back
Top