Search results

I am posting this only in order to start a thread and watch the topic. I know will need few good months in order to have Plesk working on Almalinux 10 :)

Almalinux 9 Plesk Obsidian 18.0.68 at watchdog page, seem to be version 3 release, i got the below error

I wonder if there is an ETA for PHP 8.4 . As i want to deploy in production some new code.

I have few servers where node.js was installed unwanted, behind my back . Once i remove the node.js exension, the Phusion Passenger server is not removed , is still active Why ?

OS: AlmaLinux 9.2 (Turquoise Kodkod) Product : Plesk Obsidian Version 18.0.56 Update #4, I am creating a new email account in Plesk , to a domain Still, i cannot login in roundcube after that , and i have in logs like: PHP Error: Access denied for new user [email protected]...

I have few log files , each line is quite long, more then 2000 characters ( debug informations ) Plesk File Manager is not able to open it , it display the message Unable to display the file ///httpdocs/log/error-log-2023-09-14.log: Unsupported file format. There is something on Plesk side...

If you notice in the Domains list, that the composer icon is missing then : 1. download the official composer.svg file 2. upload it to

I have several domains in Plesk, which are integrated with Gitlab for CI/CD. For each of them , i have in Plesk at Git -> Enable additional deployment actions something like below: /opt/plesk/php/7.4/bin/php /var/www/vhosts/api.domain.net/httpdocs/bin/clear-config-cache.php It is a command...

Username: TITLE catchall feature missing on Almalinux 9 Plesk web admin LXC PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE OS: AlmaLinux 9.1 (Lime Lynx) Plesk Obsidian 18.0.51 LXC on Proxmox Web Admin license PROBLEM DESCRIPTION Cannot set Catchall email for a domain I do not have in...

LXC container on Proxmox 7 Almalinux 9 Plesk Obsidian latest version When i am trying to install a trial license, i am getting Certificate signature verification failed; error info: error:03000098:digital envelope routines::invalid digest error:06880006:asn1 encoding routines::EVP lib...

when i try to run Plesk Updates, i am getting There are no products for your operating system ( 'AlmaLinux' 'Linux' '8.5' 'x86_64' ) available from the selected source.

I have a bare metal server with Centos 7 and Plesk . Static IPv4. I tried to changed the IP to a new one ( by editing /etc/sysconfig/network-script/ifcfg-eth01) and i messed something. Network not functional. Now I tried to let Plesk to change the server main ip's but the license is expired...

automatic updates failes on all servers with latest Plesk and Almalinux 8.4

Based on that announcement : Elevate it may be possible from Plesk perspective to upgrade a server with Centos 7 and Plesk latest version to Almalinux 8 , without messing around Plesk ?

I saw in Changelog for 18.0.37 : Change Log for Plesk Obsidian That mean I can try to convert a Centos 8 server with Plesk to Almalinux ? Thanks

Plesk 18.0.35 on Centos 8 I am trying to convert it to AllaLinux following this tutorial Migrate To AlmaLinux From CentOS 8 Using Almalinux-deploy Script - OSTechNix When i run the command I got the errors:

On a server with Centos 8.2 updates managed by Plesk dnf update return a list of package for Centos 8.3 But Plesk says that there are no new packages Should I update the packages with dnf ?

Centos 8.2, LXC container After upgrade to 18.0.30 I got the below warning when i run the Diagnose tool: Checking the consistency of the Plesk database Inconsistency in the table 'smb_roleServicePermissions' for the column servicePermissionId: No rows in the table 'smb_servicePermissions' with...

Everything else is working fine for the moment. Those are test servers ( trial licenses) so is not that important to have that fixed now. I have 2 different Centos 8.0 with latest Plesk: OS CentOS Linux 8.0.1905 (Core) Product Plesk Obsidian Version 18.0.25 Update #2, LXC containers...

Centos 8.0 Plesk 18.0.25 ( obviously) When you try to integrate a remote GIT repository, on a different SSH port, you may get the error: fatal: ssh variant 'simple' does not support setting port This one occur because on Centos 8, git version is : 2.18.2 and on Centos 7 is : 1.8.3.1 And...