• 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

Input Plesk can now be installed on Ubuntu 20 servers running on ARM-based platforms

williamplk said:
I have only one 1 website and it is best for me to use this small one. I can manage AWS well so I know exactly my server in AWS perform with Plesk to host my site, I now your 1-Click is best measurement but for me just 1 web site is best for me in my current situation and low cost too. Thanks
Click to expand...
1647371990066.png
 
Awesome!
Our business is working towards net zero carbon emissions (living in a climate crisis and all, it's important), and part of our transition work involves moving our production workloads onto ARM64 and in datacentres powered by renewable electricity; X86_64 is quite inefficient, with 20% die space being used for decoding instructions. ARM64 servers tend to offer much cheaper price/performance as well, so transitioning to ARM64 is a logical win-win.

We've bought licenses on the back of Plesk's arm64 support and look forward to seeing ubuntu 22.04 supported in the near future. Thank you for looking foward!
 
  • Like
Reactions: USY
Hey IgorG,

we would also welcome ARM features/support like clone and copy for the wp toolkit for the next plesk release as well.

Best wishes
 
Hi. I have problem update Plesk to Version 18.0.44 Update #2
The update is not visible in Plesk Panel
Anyone else have this problem?
 
abls22 said:
Awesome!
Our business is working towards net zero carbon emissions (living in a climate crisis and all, it's important), and part of our transition work involves moving our production workloads onto ARM64 and in datacentres powered by renewable electricity; X86_64 is quite inefficient, with 20% die space being used for decoding instructions. ARM64 servers tend to offer much cheaper price/performance as well, so transitioning to ARM64 is a logical win-win.

We've bought licenses on the back of Plesk's arm64 support and look forward to seeing ubuntu 22.04 supported in the near future. Thank you for looking foward!
Click to expand...

+1
 
event-handler.png

The only event that will successfully call the script /root/test-handler.sh is when I create a new mailbox (Mail account created).

The script is not called when I:
- create a domain
- delete a domain
- create a subdomain
- delete a subdomain.

Your assistance is appreciated
 
After upgrade Plesk Obsidian 18.0.45 and restart server MariaDB is still in version 10.3.34 not 10.3.35
Plesk team can you check it out?
 
IgorG said:
You can install it with usual Plesk installation methods. With Plesk installer in CLI, for example.
Click to expand...
Hi,

i just install the last Plesk version from the CLI:
sh <(curl https://autoinstall.plesk.com/one-click-installer || wget -O - https://autoinstall.plesk.com/one-click-installer)

on a Oracle Cloud with Ubuntu 20.04.
1658140871557.png
1658140922785.png

The installation was done successfully.


Primary VNIC​

Private IP address: 10.0.0.167
Public IP address: XXX.XXX.XXX.155

I also open all required PLESK incoming ports:
1658140707065.png
1658140727023.png

But i can't reach the Login Page:


and also not with:


What can be the reason ?
 
The listening Ports are:
root@charming-faraday:~# sudo lsof -i -P -n | grep LISTEN systemd 1 root 36u IPv4 14768 0t0 TCP *:111 (LISTEN) systemd 1 root 38u IPv6 794 0t0 TCP *:111 (LISTEN) rpcbind 714 _rpc 4u IPv4 14768 0t0 TCP *:111 (LISTEN) rpcbind 714 _rpc 6u IPv6 794 0t0 TCP *:111 (LISTEN) systemd-r 799 systemd-resolve 13u IPv4 21999 0t0 TCP 127.0.0.53:53 (LISTEN) sshd 13909 root 3u IPv4 48299 0t0 TCP *:22 (LISTEN) sshd 13909 root 4u IPv6 48301 0t0 TCP *:22 (LISTEN) xinetd 23489 root 5u IPv6 127299 0t0 TCP *:21 (LISTEN) xinetd 23489 root 6u IPv6 127300 0t0 TCP *:106 (LISTEN) sw-cp-ser 64025 root 7u IPv4 227673 0t0 TCP *:8443 (LISTEN) sw-cp-ser 64025 root 8u IPv4 227674 0t0 TCP *:8880 (LISTEN) sw-cp-ser 64025 root 9u IPv6 227675 0t0 TCP *:8443 (LISTEN) sw-cp-ser 64025 root 10u IPv6 227676 0t0 TCP *:8880 (LISTEN) sw-cp-ser 64026 sw-cp-server 7u IPv4 227673 0t0 TCP *:8443 (LISTEN) sw-cp-ser 64026 sw-cp-server 8u IPv4 227674 0t0 TCP *:8880 (LISTEN) sw-cp-ser 64026 sw-cp-server 9u IPv6 227675 0t0 TCP *:8443 (LISTEN) sw-cp-ser 64026 sw-cp-server 10u IPv6 227676 0t0 TCP *:8880 (LISTEN) mysqld 64930 mysql 47u IPv6 233547 0t0 TCP 127.0.0.1:3306 (LISTEN) nginx 74858 root 6u IPv4 253717 0t0 TCP 10.0.0.167:443 (LISTEN) nginx 74858 root 7u IPv4 253718 0t0 TCP 10.0.0.167:80 (LISTEN) nginx 74859 nginx 6u IPv4 253717 0t0 TCP 10.0.0.167:443 (LISTEN) nginx 74859 nginx 7u IPv4 253718 0t0 TCP 10.0.0.167:80 (LISTEN) apache2 79549 root 4u IPv6 269221 0t0 TCP *:7080 (LISTEN) apache2 79549 root 6u IPv6 269225 0t0 TCP *:7081 (LISTEN) apache2 79552 www-data 4u IPv6 269221 0t0 TCP *:7080 (LISTEN) apache2 79552 www-data 6u IPv6 269225 0t0 TCP *:7081 (LISTEN) apache2 79553 www-data 4u IPv6 269221 0t0 TCP *:7080 (LISTEN) apache2 79553 www-data 6u IPv6 269225 0t0 TCP *:7081 (LISTEN) apache2 79554 www-data 4u IPv6 269221 0t0 TCP *:7080 (LISTEN) apache2 79554 www-data 6u IPv6 269225 0t0 TCP *:7081 (LISTEN) master 80868 root 13u IPv4 271068 0t0 TCP *:25 (LISTEN) master 80868 root 14u IPv6 271069 0t0 TCP *:25 (LISTEN) master 80868 root 105u IPv4 271160 0t0 TCP 127.0.0.1:12346 (LISTEN) master 80868 root 114u IPv4 271169 0t0 TCP *:465 (LISTEN) master 80868 root 115u IPv6 271170 0t0 TCP *:465 (LISTEN) dovecot 80905 root 15u IPv4 273605 0t0 TCP *:4190 (LISTEN) dovecot 80905 root 16u IPv6 273606 0t0 TCP *:4190 (LISTEN) dovecot 80905 root 25u IPv4 273622 0t0 TCP *:110 (LISTEN) dovecot 80905 root 26u IPv6 273623 0t0 TCP *:110 (LISTEN) dovecot 80905 root 27u IPv4 273624 0t0 TCP *:995 (LISTEN) dovecot 80905 root 28u IPv6 273625 0t0 TCP *:995 (LISTEN) dovecot 80905 root 42u IPv4 273653 0t0 TCP *:143 (LISTEN) dovecot 80905 root 43u IPv6 273654 0t0 TCP *:143 (LISTEN) dovecot 80905 root 44u IPv4 273655 0t0 TCP *:993 (LISTEN) dovecot 80905 root 45u IPv6 273656 0t0 TCP *:993 (LISTEN) psa-pc-re 80938 postfix 3u IPv4 272836 0t0 TCP 127.0.0.1:12768 (LISTEN) named 80992 bind 24u IPv4 273948 0t0 TCP 127.0.0.1:53 (LISTEN) named 80992 bind 25u IPv4 273948 0t0 TCP 127.0.0.1:53 (LISTEN) named 80992 bind 26u IPv4 273948 0t0 TCP 127.0.0.1:53 (LISTEN) named 80992 bind 29u IPv4 274590 0t0 TCP 10.0.0.167:53 (LISTEN) named 80992 bind 30u IPv4 274590 0t0 TCP 10.0.0.167:53 (LISTEN) named 80992 bind 31u IPv4 274590 0t0 TCP 10.0.0.167:53 (LISTEN) named 80992 bind 34u IPv6 274591 0t0 TCP [::1]:53 (LISTEN) named 80992 bind 35u IPv6 274591 0t0 TCP [::1]:53 (LISTEN) named 80992 bind 36u IPv6 274591 0t0 TCP [::1]:53 (LISTEN) named 80992 bind 39u IPv6 274592 0t0 TCP [fe80::200:17ff:fe02:d4a6]:53 (LISTEN) named 80992 bind 40u IPv6 274592 0t0 TCP [fe80::200:17ff:fe02:d4a6]:53 (LISTEN) named 80992 bind 41u IPv6 274592 0t0 TCP [fe80::200:17ff:fe02:d4a6]:53 (LISTEN) named 80992 bind 42u IPv4 273955 0t0 TCP 127.0.0.1:953 (LISTEN)
 
@Ozgur The sw-cp-server service is responsible for the Plesk interface. As I see, it is running correctly and listening to the correct ports. Apparently, Plesk works correctly. So I think the problem is on the Oracle Cloud side and the firewall settings. I would reach out to their technical support team.
This KB article can help you to check out required Plesk ports: https://support.plesk.com/hc/en-us/...d-be-opened-in-the-firewall-on-a-Plesk-server
 
  • Like
Reactions: USY
You must log in or register to reply here.

Similar threads

AYamshanov
Important New Plesk webmail / SOGo Webmail extension
6 7 8
Replies
155
Views
37K
hexx_network
H
N
Resolved Plesk with ImageMagick 7.X from OS on Ubuntu 20.04
Replies
5
Views
2K
n0fear
N
randypetersen
Question After upgrade PHP-FPM has high cpu usage.
Replies
6
Views
5K
Peter Debik
P
dash
  • Sticky
Question Try our new tool to upgrade your old MariaDB server from Plesk UI
2 3
Replies
47
Views
5K
Kaspar
K
Ahmet CAVUSOGLU
Question About Ubuntu 20 Plesk Poor Performance
Replies
0
Views
594
Ahmet CAVUSOGLU
Ahmet CAVUSOGLU
Back
Top