Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
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
Not official, but given the note above and additional response from prupert on this atomicorp thread.
It appears very much safe to do on a production server.
I myself went ahead and switched the packages on CentOS 7.3 and Plesk Onyx 17 without any issues.
(I had the error after a migration...
I'd vote for it but it's unlikely to ever be a very popular request. I actually managed to get Plesk to sync with a custom location: :)
1. With `wp-config.php` in your web root (outside of your WordPress folder), the scan can detect and find your folder locations even if your WordPress folder...
Hi I am having an update issue updating Plesk 12.5.30 from Version #42 to #59.
The error log is the following:
Running rpm_check_debug
Fatal error during packages installation: [u'ERROR with rpm_check_debug vs depsolve:', 'rpmlib(FileDigests) is needed by...
I have deleted my previous answer. I was wrong. The query "ALTER TABLE `APSLicenseTypes` CHANGE `application_name` `application_name` VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL" is valid. But it triggers a MySQL error #1071.
The given error when running this query is: ERROR #1071...
Hi, I just want to cross reference this bad bug with the current 12.5.30 major update. Seem like an MU18 fix might be in order to allow Plesk 12.5.30 updates past this error. Thanks
Igor,
This kb article 123904 should also be updated to no longer create weak SHA-1 signatures past 2014 and use only sha256.
I went ahead with this added flag to regenerate mine:
openssl req -new -nodes -x509 -out httpsd.pem -newkey rsa:2048 -keyout httpsd.pem -days 3650 -sha256
Ok thanks. Disabling the Atomic repo did it.
For future reference, here are parts of the related logs.
Before:
# rpm -qa | grep -i mysql
mysql-connector-odbc-3.51.26r1127-2.el5
php-mysql-5.4.37-43.el5.art
mysql-libs-5.5.41-27.el5.art
mysql-devel-5.5.41-27.el5.art
plesk-mysql-5.5-14042516...
This is a follow-up on this problem which I am also having when trying to upgrade from Plesk 11.5.30 to 12.0.18. That resolution does not fix it the issue for me.
I followed the given resolution, removing i386 packages for both mysql and mysql-server with an x86_64 architecture, restarted, and...