Search results

Username: TITLE 18.0.58 Upgrade throws error when directory is absent PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE OS: CentOS Linux 7.9.2009 (Core) Product: Plesk Obsidian 18.0.57 Update #5, PROBLEM DESCRIPTION Upgrade to latest version Plesk release on CentOS 7.9 and...

Try excluding common cache directories and logs from your backup set to help reduce the overall footprint. Consider using a background process that doesn't use a zip approach such as Acronis (works on both Windows and headless Linux).

Your mileage might vary but the upgrade script has been known to cause the Plesk install to get wiped under certain conditions so use it with extreme caution.

Do you have any backups set to run during that time?

This is a recent issue that returns the following:

We've seen issues with the script version but they weren't consistent enough to reproduce so our SOP from now on has been to use the manual approach.

It seems contrary to logic but the TLDR version is that CentOS 8 was very quickly made end of life while CentOS 7's end of life exceeds CentOS 8 and CentOS 7 continues to be supported until June 30, 2024 so because of that oddball situation, you are able to update to the current release on your...

Apart from the one-time issue with the Dr Web Updater (see link above for quick resolution), it sounds like you might have some other issues that are worth looking into which could be caused by repository updates unrelated to Plesk. It might be a good idea to tackle one at a time (for instance...

Encryption at rest really falls under the purview of whatever third party provider is being used so it's really not related to Plesk (even though Plesk can be used to push data to those third party location such via extensions, FTP, etc...).

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?