Search results

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 ?

+1

PTR record for: 173.249.25.59 is server.autoreg.hu But the MX for your domain is mail.autoreg.hu Probably you should add server.autoreg.hu as an MX server too

1. Be sure your current Centos Plesk is up to date 2. disable in Plesk SystemUpdates-> Automatically install system package updates 3. follow this tutorial Migrate To AlmaLinux From CentOS 8 Using Almalinux-deploy Script - OSTechNix 4. after reboot, enable SystemUpdates-> Automatically install...

Hmm, it seem is working , the in-place conversion from Centos 8 with Plesk to Almalinux 8.4 with Plesk No major issues (yet)

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

can you provide more details about those fails ? there is a log file in /install folder, can you post its content ?

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:

So we have a decision from Plesk ? Change Log for Plesk Obsidian Plesk can now be installed on AlmaLinux OS. It is now possible to migrate servers on AlmaLinux OS.

Did you enabled webmail for that domain ?

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 ?

I would go for Centos 8 for the moment. Centos 7 simply does not worth the effort, too old. And will wait everybody for Facebook's decision, they are the biggest consumers of Centos 8 .

I presume that in your virtual host, where you are trying to install laravel, you have php 7.2, not 7.4 You can check and swith PHP version in Plesk -> subscriptions -> domain.com -> PHP settings The command php -v is not relevant in the virtual host context in Plesk.

Can be fixed by running from CLI the : plesk repair db -verbose But when is about to modify data in Plesk database, is always a good idea to ask first :-)

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...

Well, ok then This remind me of the same situation related to .svn folders years ago and the solution was the same: in global Apache config deny all for any .svn folders

I wonder why do you have a .git folder in your domain public folder ? Best practice for the past 10 years or so [for PHP apps at least] is to keep /vendor folder and other important folders and files outside public folder

I tested Plesk on Centos 8 using LXC in proxmox, is working flawless, only you need to install first: ssh and hostname Because Proxmox LXC Centos 8 image does not have it

Is a lack of coordination between the moment when the server is trying to renew the key and the moment when the payment crons runs on Plesk side. Example: Your monthly license expire on 13th of the month. Then on May 13 at 1 AM, your server is trying to renew the license, but there is no new...

That's annoying for me too. i am usually using subdomains, without www . mysubdomain.example.com I do not set an A record for www.mysubdomain.example.com And i keep getting daily emails with subject: Could not issue/renew Let`s Encrypt certificates for Administrator *...