Search results

In a cursory glance, I'll that that in general innodb_log_file_size should be 25% of the inndb_buffer_pool_size. Did you take a look at the actual status of MariaDB itself?

WordPress only checks for what goes 'up' and restrictions on what goes down would be at a hosting/browser level barring any specific security or other plugins at the application layer.

Question: If the log files were smaller, would the post title have been written in lowercase? ;)

To clarify, as @Linulex pointed out upthread, AlmaLinux is a repeat in that it is supported by a commercial entity that could change direction for business reasons, as evidence by Red Hat's decision. Whether that will result in the same outcome if/when/ever, is anyone's guess. There is a saying...

So did everyone back in the day with Red Hat.

Whether it be Rocky or Alma, it sounds like there might be some viable options out of the woods before the year is out yet!

I wouldn't say that they're the worst but they could use some help. It would be awfully handy if there was a "Add Website from Backup" in which you would select either a backup file path or upload one and the customer/subscription would be re-created along with its DB (assuming that it doesn't...

:)

In the event that you don't have a Plesk backup of the database in your disk image, this stackoverflow post might help you get started.

I might be overlooking something but it looks like you are running Debian 8 - I believe that the minimum supported Debian version is 9 with Plesk Obsidian.

Excellent point - in which case that's not a built-in feature of Plesk backups (backing up arbitrary directories outside of the vhosts directory).

There are a number of conditions under which a backup may not complete or may cause minor backup issues: If disk space at the time of the backup is run is insufficient A non-storage resource issue at the time of backup File thrashing (i.e. files that change in the instant that the backup job...

This issue sounds like it scales with traffic (if you always had high wait time then that might point to an underlying infrastructure issue). You can likely rule ot a Plesk-related update problem at this point so when the issue is occurring, it might help to see if the traffic loads are being...

Where you able to actually suspend the subscription? If you received an error, was it similar to this?

Out of curiosity, you placed the log file in a publicly accessible web directory?

If you're a visual guy or gal and just can't get by without a good GUI, you can also use WinSCP which enables you to upload these via a windows-style explorer interface.

The error is accurate; the URL above can't be reached so the certificate can be re-issued. Serving pages again should be the first priority then the renewal process can run.

Plesk generates the notification but the underlying issue isn't Plesk itself. You have a PHP process that is spawning children or exceed the limits of the Amazon instance that you're running so it might be a good idea to check into why that's occurring.

The first order of business is to regain access to your server. Start with SSH if you can't get into your panel and if you're not able to SSH the ask your provider for assistance to regain access (assuming that it's a virtualized server, VPS, or that they can get in).

Very quick fix if that's the case!