Plesk for Linux
kb: auxiliary
ABT: Group B
Applicable to:
- Plesk for Linux
Question
Does Plesk support RHEL 8?
Answer
Support for RHEL 8 is available starting from Plesk Obsidian 18.0.25.
Known limitations:
-
No live/in-place upgrade from CentOS/RHEL 7 to RHEL8 available. Plesk R&D team is researching this feature to support it in future Plesk releases.
-
Legacy components
mod_bw,mod_perlandmod_pythonare not available for installation. These components are deprecated. -
Currently, the following ModSecurity rulesets are available for selection: OWASP, Comodo.
-
Some third-party Plesk extensions might be incompatible with RHEL 8. In such cases, report the installation issues to the extension vendor via their support channel.
- Webalizer web-statistics feature is not available for installation as its packages are absent in the OS repository for RHEL 8. Consider using AWstats instead.
Note: as a workaround, the Webalizer package can be installed from the EPEL repository at your own risk.
Comments
53 comments
Is Docker supposed to be supported later or is this never going to work and only remotely?
Hello Mitchell van Bijleveld
Yes, it's going to be available. Work on it is currently in progress.
Do we know of a time frame for when Advanced ModSecurity Rules by Atomicorp, will be available for usage? A rough estimate.
Hi Peter, the ball is on Atomicorp side. As soon as they add support for RHEL/CENTOS 8 we will be able to use it in Plesk. To clarify ETA you may want to reach them here. Meanwhile I do recommend to use Comodo.
Docker now works on CentOS 8 (since Docker extension version 1.4.6): https://docs.plesk.com/release-notes/obsidian/change-log/#docker-1.4.6
Hi Dennis, updated article by removing Docker from known issues, thank you noticing!
Only the remote docker functionality. Docker managing on the server is still not available.
The extension seems to work, i cannot however add the Docker server.
Hi,
Thanks for the good work. I know the big difference between EL7 and EL8 (for example the dnf modules). We always used the official MariaDB (not the redhat ones) packages for the DB on EL7. On EL8 this doesn't work anymore:
Problem 1: package plesk-backup-utilities-18.0-2.centos.8+p18.0.25.2+t200325.1928.x86_64 requires plesk-mysql-server >= 18.0, but none of the providers can be installed
- package plesk-mysql-server-18.0-2.centos.8+p18.0.24.0+t200128.1353.noarch requires mariadb-server >= 5.0.60, but none of the providers can be installed
- conflicting requests
- package mariadb-server-3:10.3.17-1.module+el8.1.0+3974+90eded84.x86_64 is excluded
I understand the message because we had to disable the mariadb module because we wanted to use the MariaDB packages. Right now:
MariaDB-common-10.3.22-1.el8.x86_64
MariaDB-server-10.3.22-1.el8.x86_64
MariaDB-client-10.3.22-1.el8.x86_64
Fix:
Adding the official MariaDB packages to the required list in the RPM is very easy (did it myselves a couple of times). Check https://rpm.org/user_doc/boolean_dependencies.html . With this trick you can have a dependency on mariadb-server AND MariaDB-server.
I would like to use CentOS 8 soon, so I check this article regularly. I am mainly interested in whether Atomic now supports ModSecurity. If you update the page, which contains a list of problems, it would be nice to know if you have removed or added items. I can only see that a change has been made to the article, but not what exactly.
Some questions about Docker: I know that Red Hat 8 (and so CentOS 8) supports Podman, instead Docker.
Will be there ripercussions on Plesk after this change?
Is there any Eta for Plesk container support (not only remote) on CentOS 8?
Finally: could I install Podman / Docker on CentOS 8 + Plesk or there will be some bug / crash?
Thanks in advance.
I performed a migration from an old server with Centos 7 to Centos 8 today. Some options related to mod_bw are still displayed in the service settings.
Is this a bug? Is there a way to remove them?
Hi Francesco Zanti,
It's the first time I hear about Podman, and I'm not aware of anything regarding this in Plesk.
I encourage you to create a UserVoice request.
Hi Sebastian Ayala,
This happens because, on CentOS 8, your Plesk installation has mod_bw. It's expected, and if you don't want it the only way is to remove such component.
Hi Francisco Roman Garcia Rodriguez,
thanks for your support: Would Docker be supported with CentOS 8 in next release? Could I safely install Docker on the same server of Plesk?
I will create a UserVoice!
> Atomic did not yet release their ModSecurity rules compatible with CentOS 8/RHEL 8, since it is not available for selection at Tools & Settings > Web Application Firewall > Settings.
What exactly does that mean? atomicorp community support said:
> The rules are supported on any platform that supports modsecurity, that includes Centos 8.
Hi,
Pls advise if EPEL and Remi Repository can be installed on Centos 8/Plesk
https://webhostinggeeks.com/howto/how-to-enable-epel-and-remi-repository-into-centos-6/
Hello Adrian Chan
On servers with Plesk it's recommended to use repos provided by Os vendor only. Otherwise, this may lead to dependency issues during Plesk updates or components installation.
Hello Karl May
Sorry for the late response.
Let me double-check this.
@Karl May,
According to Atomicorp support, RHEL 8 is already supported and they have plans to add CentOS 8 support later this year.
Thank you for bringing this to our attention, stay tuned for the changes in this article.
After a succesfull install of Plesk Obsidian 18.0.27 on a fresh and updated CentOS 8 system, I can't login to Plesk for a "Connection Refused" error.
Command "iptables -F" resolves the problem. Why this occours? How can I solve this problem?
Thanks in advance!
After a succesfull automatic install of Plesk Obsidian 18.0.27 (via SSH) on a fresh and updated CentOS 8 system, I can't login to Plesk for a "Connection Refused" error.
This is the output for iptables, after Plesk installation:
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT icmp -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
Chain FORWARD (policy ACCEPT)
target prot opt source destination
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
As you can see, there is no entry for httpd, so connections on port 80 and 443 are refused.
I tryed also witch web installation, and same problem occuorred.
Command "iptables -F" resolves the problem. What's wrong?
I can add an iptables rule manually, ...and then?
Thanks in advance!
Nico Timeo to manage it in a nice way and store permanently please install and enable Firewall module:
https://support.plesk.com/hc/en-us/articles/115001078014--How-to-manage-local-firewall-rules-on-a-Plesk-for-Linux-server
Any support for cGroups on CentOS 8? RHEL/C8 fully supports cGroups.
Plesk's Firewall module isn't as flexible as manual nftables/iptables rules so make sure to backup any rules before you enable it.
@Razvan Rosca as I can see the questions was addressed in the ticket
@Ivan Postnikov
Is there any news about Atomicorp and Modescurity yet? I would like to rent a new CentOS 8.2 server and use "Atomic Advanced" there.
Karl May There are still no issues about Modsec on Centos 8. Please monitor this article for future changes https://docs.plesk.com/release-notes/obsidian/change-log/
Seems that Backup Task limitation dont work under CentOS 8,
I've limited to 4 Backup Tasks at the same Time, but "top" says 12 backupmng are running. I've set it up to not compress the backups
Any news on KernelCare? They have a blog post from last year claiming support for CentOS 8 - https://blog.kernelcare.com/kernelcare-supports-centos-8-automated-live-patching
Please sign in to leave a comment.