Search results

# cd /var/lib/mysql # ls -la

Please check whether Fail2Ban is blocking your own public IPv4 address (e.g. for too many false login attempts). You can either search for it in /var/log/fail2ban.log or search the list of banned ip addresses in Tools & Settings > Fail2Ban

This is an easy task for Fail2Ban. Plesk comes with a jail named "Dovecot". Simply activate that jail. It'll monitor the mail log for failed login attempts and ban the IP addresses of the users who send n false logins.

Some services like MS Office 365 won't accept this number of mails for delivery, regardless whether you send them all at once or with a delay. You'd need a much longer delay like 10 minutes or more and send tranches of 50 mails only. They might accept the mails, but they will not deliver them to...

It is under discussion, but there are no specific plans yet. I'd not count on this to be ready in time.

Do you see your database directories and files in /var/lib/mysql?

What is the value of session.gc_maxlifetime when you display phpinfo()?

Is mariadb running (systemctl status mariadb)? If it is not, what log entries do you find in your syslog on mariadb that describe why it does not start?

The issue frequently occurs when the firewall is blocking the passive ports range. You could first check the Plesk Firewall whether the FTP passive ports are allowed. This KB article gives more advice on it...

Most commonly this error is caused by a lack of disk space. Please check whether your / partition has enough space left.

"Session token has expired" is normally an issue with the PHP session management, not the webserver. Closing and re-opening the browser might solve it.

If "client_max_body_size 128m;" doesn't do it, why not try 1G instead?

Thank you for clarifying. I now tried it with "Connection info", but could not reproduce the issue. When I click on the close field, only the password overlay is closed, not the drawer.

When you use the "Wordpress" menu and click "Install" to install a fresh Wordpress, the WP toolkit creates a new database for you. But you can also take the route you took, it works, too.

Please compare the database configuration entries in your wp-config.php files of the two domains. They likely use the same database.

You could try to comment the line 25 1 * * 6 root /opt/alt/tmpreaper/usr/sbin/tmpreaper 168 /var/imunify360/tmp (add a # as the first character of the line).

Most certainly this issue is not related to the Plesk software. Instead, some serious underlying issue must exist. I'd guess that when the server is slow in rescue mode, it is hit by a DDoS attack where some requests come through. Did your provider mention this? Did they check it? If you have...

I admittedly do not know specific and reliable answers to your questions. I'd always plan many hours for an upgrade procedure. You cannot downgrade if things go wrong. If possible in any way you could consider having a staging server where you practice all necessary steps. My experience here is...

It's not. What are the exact log entries including the ones not referring to SSL?

You can either specificy the full path as suggested or you can start from httpdocs (without slash in that case).