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
I don't necessarily need to erase bind from this box.
I just want to get rid of the above mentioned mount points. If they are gone, my CDP/Idera backups will start functioning without needing any other modification to the box.
Hello,
@Faris Raouf: I don't have bind-chroot rpm/package installed.
CentOS community tells me these mounted links won't be there without installation of bind-chroot rpm/package. So its not the OS.
Also, from going through other threads on the forum and through google search, I note that...
There are two ways, actually three ways to get this to work, that I can think of;
(1) Try installing latest updates for Plesk
or
(2) Try uninstalling php, as well as php related packages installed by plesk. Try reinstalling the PHP Server Component
Be careful with this option. Only do this...
Hello,
The problem occurs because the chrooted implementation of bind from plesk envolves cyclical symlink references. They are as following;
/etc/named 16G 2.0G 13G 14% /var/named/chroot/etc/named
/var/named 16G 815M 15G 6% /var/named/chroot/var/named...
Hello,
(1) If you have Plesk 11 installed on your box, you can run;
- /usr/local/psa/admin/bin/autoinstaller --select-release-current --install-component phpgroup
The above mentioned command needs to be run on shell/CLI. Root access is required.
The other way to do it is to go to login to...
Hello all,
I have plesk 11 installed on CentOS 6.3 (64-bit). Updated to the latest update.
We have our own DNS implementation based on Power DNS+MySQL. We do not utilize bind or Plesk's implementation of bind.
In this specific instance, its causing problem with CDP/Idera (previously...
I'm exporting plesk license key from Plesk 8.6.0 server in the above mentioned way.
When I import this key to our new Plesk 11.0.9 server, it fails via CP, saying -> Error: Invalid key: Unknown key format
Please advise.
Hello,
We have plesk 11 on this box.
I have a domain. Its housed on a shared IP. I need to have it hosted ONLY on port 80. I dont want the webserver responding for it on port 443.
How can I achieve this ?
CentOS Community tells me;
(1) No openssl 0.9.8f or later for CentOS 5.8
(2) Upgrade to CentOS 6.x to get openssl version later than 0.9.8e
(3) openssl 0.9.8f (at least) is what SNI depends on as per this URL ( http://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI )
This means, I can't...
SNI needs openssl 0.9.8f or later to function.
CentOS community says NO openssl 0.9.8f or later for CentOS 5.8 release/branch. 5.8 is the latest available in 5.x branch for CentOS. openssl 0.9.8e is the latest your going to get with CentOS 5.8
I'm told Upgrade to CentOS 6.x to use SNI...
Isn't that drastically insecure way to do migration ? Repeatedly transmit root password over network wire all throughout the migration process ?
Why has the sudo user way been removed from PMM ? It worked great "as it was".
It needed improvements like also migrate horde or squirrelmail...