Search results

You might try GitHub - sixhop/AutoMySQLBackup: A fork and further development of AutoMySQLBackup from sourceforge. http://sourceforge.net/projects/automysqlbackup/ as a starting point or even easier, as of Plesk Obsidian 18.0.54 the ability to back up databases separately has been added in the...

Looks like your DNS zone is at GoDaddy and you're missing that txt record: https://mxtoolbox.com/SuperTool.aspx?action=txt:_acme-challenge.[redacted]

If you're able to replicate this error, please also consider reporting a bug.

Replicated this issue on Cent OS as well as Debian and Ubuntu and created a bug report. Hopefully the development folks add a high priority to this fix!

Username: TITLE Scheduled Backups Fail in Plesk Obsidian 18.0.47 PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian v18.0.47_build1800220923.10 os_CentOS 7 CentOS Linux 7.9.2009 (Core) PROBLEM DESCRIPTION After updating to Plesk Obsidian 18.0.47, scheduled backups...

It sounds like a code issue which would be outside the purview of this forum. You might consider visiting the WordPress forums for assistance with this if you're working with a framework or builder plugin.

TLDR; This isn't a Plesk issue but rather an application layer and/or application configuration question. Your builder may use the WordPress website's language settings so you might want to start with that: WordPress dashboard and go to Settings > General. You can also change the desired...

Indeed - My concern is that while it will be fixed for future updates will the "Run upgrade with option --repair to rerun failed steps." need to be manually run on installations that have already been upgraded?

Question: Will the upgrade need to be re-run or while the fix for PPPM-13114 fix it for already upgraded installs?

The underlying disk subsystem is going to very much play into this. Running databases on the same instances (making assumptions about IO) is certainly achievable and can simplify the setup but mail at scale can create headaches. If anything, consider keeping your mail on its own clusters as...

Are you moving this database between two servers or copying it on the same server?

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?