Search results

The system is going down for halt in 7094 minutes! Seems to work

Hello, to increase php memory_limit , you can edit directly the php.ini configuration in Tools & Settings > PHP settings > php version you want to use to run your cronjob. Then go in the tab php.ini and find the variable memory_limit

Hello, the easiest will be to add a cronjob with the command crontab -e , and to add the following line : 0 3 25 * * /sbin/shutdown now

When I update my robots.txt file, it's also updated when I browse mywebsite.ltd/robots.txt : In Plesk editor : With my web browser :

Hello, robots.txt file is located in your website root folder (probably httpdocs) . But this file isn't managed by WordPress toolkit, and will probably never be managed by WP toolkit. The content you have posted previously is most of time defined by the plugin Yoast SEO. Not by Plesk.

Hello, the easiest in your case will be to use your Plesk server as nameservers for your domain. This way , when you will add a new subdomain, the proper DNS records will be added automatically. To do so, you need to : - set Glue registry for your domain : to set your nameservers IP to...

Hello, to do the same , the file to edit is /opt/psa/admin/htdocs/theme/css/main.css on Ubuntu/Debian or /usr/local/psa/admin/htdocs/theme/css/main.css on Centos

It will probably be easier from PMA, just select tables and go into operations tab. It's not safe at all and it's not needed. Each application use particular storage engine depending on it needs. If MyISAM is required on some tables, and InnoDB on some other, there is a reason...

No, if some tables require MyISAM to use FULLTEXT indexes for example, you can't convert them to InnoDB.

Hello, WP-Tookit keep them in cache with an expiration date. It will remove them automatically. You can disable cache by adding the following directives in your panel.ini file (with the panel.ini editor extension or directly in /usr/local/psa/admin/conf/panel.ini) : [wpToolkit]...

You are right, there is maybe an error in the kb title. The easiest to use the MariaDB release of your choice is to install it before installing Plesk : #add MariaDB 10.1 repository curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | sudo bash -s --...

You have to backup the folder /var/lib/mysql , then to totally remove MariaDB. After that, update yum repo to apply the change in /etc/yum.repos.d/MariaDB.repo, and reinstall MariaDB 10.1. The last step is to restore the previous database and to apply the MariaDB downgrade. This...

You have to edit your table configuration to use MyISAM instead of InnoDB using phpmyadmin :

It's exactly the same process on Centos than on Ubuntu. Replace MariaDB 10.2 repo by MariaDB 10.1 repository. nano /etc/yum.repos.d/MariaDB.repo Should currently look like : # MariaDB 10.2 CentOS repository list - created 2017-12-17 13:44 UTC #...

Hello, your issue isn't related to MySQL or MariaDB, but to the engine storage used. To be able to use FULLTEXT indexes, you have to use MyISAM instead of InnoDB. MySQL Bugs: #6713: The used table type doesn't support FULLTEXT indexes

You can generate a password directly via ssh with the command : dd if=/dev/urandom bs=1 count=32 2>/dev/null | base64 -w 0 | rev | cut -b 2- | rev But it will be more secure to disable password authentication via ssh, and to use ssh-keys, and to use another port than 22 to...

This is not a bug, it's only logic linux permissions . Plesk will never use root owner in user directory.

You are right. That will be great to add the information "support Plesk Multi Server update#X" in the plesk catalog.

Hello, it's probably the fact that you are using Multi-Server extension. I have no idea if Google login is available with Multi-servers configuration.

Hello, You can try to disable the logrotate cronjob, but I do not think it's the current issue. Have you check the 14MB of error logs you have ? It may help you to find the issue