Search results

Based on that screenshot, the zone for your domain name is located at charlestonroadregistry.com. Did you mean to point the domain's name servers to use your Plesk server's DNS service or another?

It sounds like you're missing DNS records. Check first to see if your domains resolve to the expected name servers with a simple tool like Network Tools: DNS,IP,Email. Look at the name server that is queried and from there you can determine where the zone actually resides.

If that table is truly corrupt, take a backup of it and then try these steps before restarting your MariaDB instance.

What does your my.cnf look like? On that note, do you by any chance have a back up of either the servers table?

There are three places to check: The website's error log in Plesk Enable the WordPress error log file The error log for your PHP handler For a site that isn't yet launched, this sounds more like an uncontained code leak however it's too soon to tell. Be sure to check to ensure that Apache is...

As they're both owned by the same entity one would think a little cross-knowledge might go a long way here. Indeed, using CloudFlare with Fail2Ban can be a challenge so hopefully the friendly folks at Plesk will give it a hard look as part of their roadmap.

You might be running into issues with CloudFlare and Fail2Ban but more information about your setup is needed.

Truly one of the best approaches to a seamless issuance/renewal process!

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...