Search results

https://mariadb.com/kb/en/mariadb-package-repository-setup-and-usage/ curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --mariadb-server-version=mariadb-10.6 --skip-maxscale

This should help you. However, I always upgraded via SSH. Add the desired MariaDB repository, yum update Maria DB*, then MYSQL_PWD="$(cat /etc/psa/.psa.shadow)" && mysql_upgrade -uadmin

Upgrade to MariaDB 10.6 on the new server. It is the longest supported MariaDB version.

403 on robots.txt. Check the mod security log, since the Nginx error log doesn't have any entries. I would also set up mod_realip in nginx so that the real visitor IP gets logged: Module ngx_http_realip_module

Extension updates are controlled from the extension catalog URL set in panel.ini. Furthermore, extensions might not be available on older Plesk or OS versions. You can curl the Plesk extension catalog on each server to see what versions are returned for both your servers. The output will be...

Interesting. You might be facing this issue: https://support.plesk.com/hc/en-us/articles/12376955103511-Migration-to-another-Plesk-server-fails-Unable-to-restore-DNS-zone-from-a-backup-Incorrect-DNS-record-values-were-specified-example-com-IN-Record-Type-example-com-ttl-0

So, on the new server adding a new temporary domain doesn't have the DNS settings? How did you install the DNS service?

Any security plugin like Wordfence or security application like modSecurity or Imunify360?

Check at the exact date and time in the error log. Checking the log file directly might be easier. The log entry will not say 403. It will say something else, why do you get a 403.

That is from the access log, not from the error log. The error log will contain additional information regarding the 403 request. It might also be in the php-fpm error log (/var/log/plesk-php83/error.log)(replace 83 with the PHP version)

Do you send the traffic from Cloudflare to the correct IP address?

Check the corresponding entry in the domain error log or in the global php-fpm log

The provided link has a docker-compose how-to. However, Plesk Docker extension is not yet compatible with docker-conpose. The article also says how to build the Docker nodes manually (Docker Chatwoot Production deployment guide | Chatwoot). You will need 2 empty folders and in each folder a...

The DNS service doesn't work at all or one or several domains don't have the proper DND records that were set on the old server? For the first, the service might not be installed or running For the second, there might be restore errors during the DNS zone import

The created Plesk backup encrypts the passwords with the install key or with a password. Since you restored the Plesk backup on a new install the install key was different and it couldn't decide the passwords, generating new passwords for all accounts Export the backup you want to restore from...

Hi, Automatic wildcard Let's Encrypt certificates renew automatically if the domain DNS zone is hosted in Plesk, or Plesk can send the new domain ownership verification string to the authoritative DNS zone. Since you have to renew manually I suspect this is the case. You have 2 options: 1)...

The new email accounts list has a bug PPPM-14685 There is a workaround. Disable the new UI for the email accounts list from panel.ini: [navigation] smb.mail.useNewEmailList = false

I suspect you are missing a dot at the end of the NS records from the DNS template. In the DNS zone, you can have the record "test" but it will automatically append the domain name. However, adding the record test.domain.tld. will not append the domain name. The same is valid for the DNS record...

Ok. So it was from the CentOS repository. Try the above to update the currently defunct repositories

Looks like you have a problem with the repositories. Please have a look at GitHub - AtlasGondal/centos7-eol-repo-fix: CentOS 7 has reached its End of Life (EOL), which means its repositories may no longer be maintained and accessible. However, you can still use some workarounds to keep your...