On the Settings page you decide what applies to the whole website: notifications, performance, exclusions and log. The page also shows whether the task sources are running, and gives you the report for support.
Settings that belong to a backup plan or to a target are not set here, but at the plan or at the target. More on this: Backup plans: tile and form and The “Targets” page.
The page at a glance
- Settings is the menu item of the page, in the WordPress menu under cloneworx.
- The main tile uses colour and text to show whether operation is running. Below that are the last run of the scheduler, the state of the log and the recipients of the notifications.
- Notifications is expanded when you open the page.
- System and support, when expanded, shows the state of the server and gives you the support report.
- Backup encryption sets up the recovery key for encrypted backups. The tile belongs to cloneworx Backup Pro.
- Key shows what protects the key for the passwords, and renews it.
- Extended switches to the view with all tiles. The choice applies to all pages of the plugin.
The following applies to every tile on the page:
- Expanding and collapsing. A click on the title row or on the arrow expands a tile and collapses it again. The arrow shows the state that comes next. When you open the page, all tiles are collapsed; only Notifications is open. The main tile cannot be collapsed.
- Saving. Every tile saves on its own. A switch saves immediately. You save fields with Save in their tile; the page then reports Saved.
- Rejected values. If the server rejects a value, it saves nothing. The value stays in the field, and the reason is shown in red below it, for example Allowed: … to ….
- Messages. The message appears below the main tile. A green message closes by itself after 8 seconds. Yellow and red messages stay until you close them or start something new. A red message takes you to the global log with Show global log or, after a diagnosis, to the log of that diagnosis with Log.
The main tile
The main tile assesses operation. To do so, it checks whether a task source that starts scheduled backups arrives on its own. The tile reloads its state every 60 seconds.
- The result for operation. The border of the tile and the cogwheel have the colour of the result.
- Send test email sends an email to the recipients of the notifications. The page then reports which addresses the test email was sent to.
- Copy support report copies the support report to the clipboard. What it contains is described below under “System and support”.
| State | Meaning | What you can do |
|---|---|---|
|
green Everything is ready. |
No plan is active, or an automatic task source has run in the last two hours. If none has ever run, the tile stays green until nothing has happened at an active plan for more than two hours: no change, no run. | Nothing. |
|
yellow No automatic task source has run for …. |
A plan is active, but no automatic task source has run for more than two hours. A scheduled backup may then be missed. | Set up a system cron: Start backups on time: set up a system cron. |
|
yellow No automatic task source has run yet. |
A plan is active, nothing has happened at it for more than two hours, and no automatic task source has ever run. | As in the row above. |
|
red Requirement missing: … |
The website does not meet a requirement of the plugin. | The message names the requirement. |
Below the result are these details:
- Last scheduler run shows the time and, in brackets, the kind: WP-Cron, Wake event, WP-CLI or end of a job. The browser does not count here: it is only available while someone has a page of the plugin open. If there has been no run, it reads never.
- Log writable shows OK or the reason why the log cannot be written.
- Notifications go to shows the recipients.
- A red line appears if WordPress could not hand over an email from the plugin: The last email could not be sent: … The line shows the reason and the time.
If the server runs a 32-bit PHP, an additional line in orange appears below the result: This server runs a 32-bit PHP. cloneworx Backup works here, but a backup or restore stops as soon as it would exceed …, because larger sizes cannot be counted safely on 32 bit. The limit is 1.5 GiB per backup. The same warning appears in the plugin list of WordPress.
Notifications
- Email addresses accepts up to 5 addresses, separated by commas. If the field is left empty, the notifications go to the admin address of the website; the field then shows this address in grey.
- On errors and warnings sends an email when a backup ends with an error or with warnings. The default is on.
- On success sends an email after every successful backup. The default is off.
- When the last valid backup is older than the plan allows warns you when a scheduled backup does not take place. The default is on.
- Save saves the addresses. The switches save immediately.
- Subscribe to the newsletter opens the cloneworx sign-up form in a new tab.
The field rejects an invalid address and too many addresses: One of the addresses is not valid. or At most … addresses.
With the switch On errors and warnings, an email is also sent when a restore fails or is undone, when a check finds a damaged backup and when a scheduled run could not start. No email is ever sent for a backup that you abort yourself.
A plan counts as overdue when its last valid backup is older than its rhythm plus a tolerance. The tolerance is half of the rhythm, at least 6 hours: a daily plan is overdue after 36 hours. The plugin then sends an email and, after that, a reminder every three days. The next valid backup of the plan ends the warning.
Switching off “On errors and warnings”
Without this notification you are not told when a backup fails. The plugin therefore asks: Switch off notifications? Only Yes, switch off switches it off; Cancel leaves the switch on. As long as the notification is off, the Overview page shows a red message every time it is opened.
Step by step: Set up email notifications.
News and updates
At the end of the tile there is a sentence with the link Subscribe to the newsletter: Support us so that we can keep making great plugins. Get news (really rare ☝️) and updates on cloneworx by email. The link opens the cloneworx sign-up form at register.cloneworx.de in a new tab, in the language of your dashboard. The plugin itself sends nothing: you enter your address there and confirm it with the link in the email you receive. Every news email contains an unsubscribe link.
The Extended view
In the Extended view the page shows seven more tiles, and System and support gets the block Diagnosis.
- Scheduler shows which task sources arrive on this server and gives you the lines for a system cron.
- Performance defines how long a step works and how long the pause is afterwards.
- Retention defines how many backups without a plan are kept per target.
- Exclusions contains the rules for files and folders that never go into a backup, and the tables for which only the structure is backed up.
- Global log defines how long logs are kept, switches debugging on or off and shows the global log.
- System and support is in both views.
- Backup encryption is in both views.
- Key is also in both views.
- Licenses shows the license of the plugin and of the bundled components.
- Uninstall defines what is removed when the plugin is deleted.
- Compact switches back.
Scheduler
A backup runs in many short steps. A task source triggers the plugin: it starts the next step of a running job and makes the plugin check whether a plan is due. The plugin checks whether a plan is due on these task sources:
- WP-Cron, with the plugin's own task every 15 minutes (with cloneworx Backup Pro every 5 minutes) and with the wake-up event,
- the open Overview or Backup page, every 60 seconds,
- the end of every job,
- WP-CLI, including via a system cron.
A job that is already running is also continued by the self-request of the server. The tile shows which task sources arrive on your server.
- WP-Cron is active or runs in the alternate mode (ALTERNATE_WP_CRON). The dot is yellow if WP-Cron is switched off. Then it reads switched off by DISABLE_WP_CRON; only a system cron or WP-CLI runs the schedule.
- Plugin task (every 15 minutes) shows when the plugin’s own task in WP-Cron last ran. Green means it ran in the last two hours. Otherwise the dot is yellow, or grey if WP-Cron is switched off.
- Last tick shows the last automatic task source with time and kind. Yellow means a plan is active and no automatic task source has run for more than two hours, or none has ever run. Grey means none has run yet and no plan is active.
- Self-request shows whether the server can reach itself; the plugin records this for every job. Green is works; last arrived …, red does not arrive: … with the reason, grey not checked yet.
- Wake event shows the time at which WP-Cron wakes the plugin for the next run. The plugin sets the event to the earliest next run of all active plans. Without a wake event the dot is grey.
- Next run shows the plan that runs next and its scheduled time. Without a scheduled time the dot is grey.
- Missed runs lists the missed runs of the active plans. Green means no plan has missed a run. Otherwise the dot is yellow.
- Check task sources starts a short probe run that the page only observes.
- Copy is next to each of the two lines for the system cron and copies that line to the clipboard.
A scheduled time counts as kept if a task source runs within one hour of that time, or if the time fell within a running job. After that it counts as missed: nothing starts, and the plan moves on to its next regular time.
Check task sources
While the probe run is running, the following appears next to the button: Probe run started; waiting to see which task source runs it … At the end a message shows the task source of the last call: Probe run finished; last call from: …. As a rule, that is the self-request. Below it are Last WP-Cron tick: …. and Last WP-CLI tick: …. Both lines show date and time, or never so far if this task source has not run since the plugin was installed. The probe run itself is over within a few seconds; only these two lines therefore show whether a system cron arrives.
If no task source runs the probe run for a minute, the tile reads: No task source has run the probe for a minute: the self-request and WP-Cron do not work here. Set up a system cron with the line below. Next to it, Abort probe run ends the probe run.
The lines for the system cron
The reason is given above the two lines: Without visitors WP-Cron does not run and a scheduled backup is missed. A system cron every five minutes makes the schedule independent of visitors:
Both lines are filled in for this installation. They are alternatives: the word or is between them, one of the two is enough, and each has its own Copy button. The first calls wp cloneworx-backup scheduler tick every five minutes and is the preferred option. Below it is this note: This cron job must start as the user under which the web server runs WordPress (e.g. www-data). Otherwise the created files belong to the wrong user, and the website cannot change or delete them later. The second calls the file wp-cron.php of your website every five minutes. Below it is this note: May be run by any user; the web server executes the code itself. How you enter the line with your hosting provider is described in Start backups on time: set up a system cron.
Performance
On web servers, PHP is stopped after about 30 seconds. The plugin therefore works in short steps: every step works, saves its state and ends; the next one continues from there.
- Maximum time per step defines how long a step works at most before it stops.
- Pause between steps is the waiting time after every step before the next one begins.
- Save applies both values.
- Shared hosting preset enters 10 seconds and 2 seconds into the fields.
- Default enters the defaults into the fields.
| Field | Default | Allowed |
|---|---|---|
| Maximum time per step | 20 seconds | 5 to 20 seconds |
| Pause between steps | 0 seconds | 0 to 60 seconds |
Both buttons only fill the fields; only Save applies the values. The maximum time can never be more than 20 seconds. If the server aborts steps, the plugin lowers the effective value on its own. There is no setting for compression. More on this: Adapt the plugin to your server.
Retention
The tile has one field: Max. backups without a plan. Back up now runs a plan; a backup without a plan is created only with WP-CLI. Backups without a plan form a group of their own. The field defines how many valid backups of this group are kept per target.
The default is 7; values from 1 to 99 are allowed. The field saves as soon as you leave it; the tile has no button for saving. For backups of a plan, Max. backups at the plan applies: Define how many backups are kept.
Exclusions
The rules of this tile apply to the whole website and to every plan. You choose what a plan backs up at the plan; you define here what never goes into a backup. The plugin’s own folders are always excluded. You set additional rules for a single plan in the form of the plan: Backup plans: tile and form.
- The note says which rules are in effect: The default rules are in effect. or Your own rules are in effect.
- A rule. The cross after it removes it from the list.
- Folder, name with * or extension is shown in the field for a new rule.
- Add puts the new rule at the end of the list. The Enter key does the same.
- The line lists folders that other plugins announce through their constants. These folders are always excluded, even if they were moved. The line appears only if there are such folders.
The default has 28 rules: caches and temporary storage, folders of other backup plugins, logs and system leftovers, Git folders. Adding and removing only change the list on the page at first. The rules are saved with Save at the end of the tile.
| Rule | Meaning | Example |
|---|---|---|
| Name | A file or a folder with exactly this name, at any depth. | Thumbs.db |
| Name with a slash at the end | Like the name alone, but only folders. | updraft/ |
| Name with one asterisk | A name that ends or begins with the text. The asterisk is at the start or at the end, never in the middle. |
*.log, backwpup*
|
| Path | A path in a root; the first part is the name of the root. The rule matches the entry and everything below it. An asterisk is allowed only in the last part. | wp-content/cache |
Path with **
|
** as a whole part stands for any number of folders, including none, as in .gitignore. wp-uploads/** matches everything in the uploads. At the start, **/Thumbs.db is the same as Thumbs.db. |
wp-uploads/**/*.jpg, wp-uploads/**/cache/
|
The roots are called wp-content, wp-uploads, wp-plugins, wp-themes, wp-mu-plugins, wp-core and wp-root. Upper and lower case do not matter in the comparison. The rules follow .gitignore, with two differences: a path begins with a root, and there is no ! to negate a rule.
The plugin checks every rule when saving. If a rule is wrong, it saves nothing, and the reason is shown in red at the rule. Remove it with the cross and enter it again correctly.
| Reason at the rule | Example of a wrong rule |
|---|---|
| must not start with a slash | /wp-content/cache |
| empty part in the path | wp-content//cache |
| “.” and “..” are not allowed | wp-content/../cache |
| only one * is allowed | *bla* |
| * only at the start or the end of the name | a*b |
| * alone is not allowed | wp-content/* |
| * only in the last part of the path | wp-content/*/x |
| **/ at the start works only with a single name after it; otherwise start with a root | **/a/b |
| unknown root: use wp-content, wp-uploads, wp-plugins, wp-themes, wp-mu-plugins, wp-core or wp-root | content/cache |
| the path runs through the folder of another root and never matches; write it as … | wp-content/uploads/videos |
| the path names the folder of another root; a whole root cannot be excluded | wp-content/uploads |
| contains characters the database cannot store (for example an emoji) | a rule with an emoji |
| is not valid UTF-8 text | a rule with characters in another encoding |
| contains control characters | a rule with a tab between two characters |
A rule saved earlier that runs through the folder of another root shows the reason in red in the list.
The default rules
Caches and temporary data
| Rule | Excludes |
|---|---|
wp-content/cache |
WP Super Cache, W3 Total Cache, WP Rocket |
wp-content/upgradewp-content/upgrade-temp-backup
|
WordPress updates |
wp-content/wflogs |
Wordfence firewall data |
wp-content/litespeed |
LiteSpeed Cache |
wp-content/et-cache |
Divi |
wp-uploads/wc-logs |
WooCommerce logs |
Folders of other backup plugins
| Rule | Excludes |
|---|---|
wp-content/updraft |
UpdraftPlus |
wp-content/ai1wm-backups |
All-in-One WP Migration |
wp-content/duplicator-backupswp-content/backups-dup-litewp-content/backups-dup-pro
|
Duplicator |
wp-content/wpvividbackups |
WPvivid |
wp-content/aiowps_backups |
All-In-One Security |
wp-content/wpclone-tempwp-uploads/wp-clone
|
WP Clone |
wp-uploads/backwpup* |
BackWPup |
wp-uploads/backupbuddy_backupswp-uploads/pb_backupbuddywp-uploads/backupbuddy_temp
|
Solid Backups |
wp-uploads/wp-staging |
WP Staging |
wp-uploads/snapshots |
Snapshot |
Logs and system leftovers
| Rule | Excludes |
|---|---|
error_logdebug.log*.log.DS_StoreThumbs.db
|
in every folder |
Git folders
| Rule | Excludes |
|---|---|
.git |
the folder of a Git checkout, at any depth. It holds every earlier version of every file, grows with every update and is not needed to restore the website. |
The rule .git applies to websites without stored rules of their own and after a click on Reset to defaults. Stored rules of your own stay as they are.
Tables as structure only
Below the rules is the part Tables backed up as structure only. The rows of these tables are missing from every backup. During a restore, such a table stays as it is on the website, with its data. If it does not exist there, the plugin creates it empty. By default no table is ticked: every table is backed up in full until you change it yourself.
- A group of candidates: Sessions, Logs, Caches or Statistics. Candidates are tables of known plugins that exist on this website.
- A table with checkbox, name without prefix, rows and size. If it is ticked, only its structure is backed up.
- Other tables shows ticked tables that are not candidates.
- Table name without the prefix is shown in the field that you use to add any other table of this website.
- Add table ticks the named table. The field rejects an unknown name: This table does not exist on this website.
- The line lists the plugin’s own tables. For these, only the structure is ever backed up.
- Save saves the rules and the selection of tables.
- Reset to defaults immediately restores the default rules. The button saves the selection of tables as it is on the page.
- Statistics tables contain the visitor numbers themselves. If only the structure is backed up, the numbers are not in any backup: if the table is lost, they are gone.
- If there is no candidate on the website, it reads: No known log, session, cache or statistics table on this website.
- If a second WordPress installation with a longer prefix is in the same database, the plugin does not back up its tables and reports them: Not backed up: … tables of another WordPress installation with prefix “…”.
Step by step: Define what gets backed up.
Global log
- Keep logs for accepts 7 to 365 days; the default is 30. After this time the daily maintenance of the plugin deletes the global log and the logs of the individual jobs.
- Debugging for 24 hours writes detailed lines into the log and switches itself off after 24 hours. The switch saves immediately.
- Log writable is green with OK or red with the reason.
- Save saves the number of days.
- Download all logs downloads all logs of the plugin as one tar file.
- Show global log opens the global log in the dialog window Global log.
- The state of debugging is shown below its switch: Debugging is on until …. or Debugging is off. Switch it on for 24 hours when you need detailed logs.
- The global log contains everything that cloneworx Backup and cloneworx Backup Pro write: connection tests of the targets, changes to the settings, the schedule and every line of every job. The log of a job contains the lines of that job once more, on their own. The global log has one file per day. If the plugin writes more than 5 MB into it on one day, it accepts only warnings and errors for the rest of that day; at 10 MB it ends for that day. The dialog window shows the last 500 lines with date, time, level and message. The lines are in English.
- The tar file is called
cloneworx-backup-logs_<host>_<date>_<time>.tarand is not compressed. It contains the global log with one file per day and one log per job.
More on this: Read the log.
System and support
The tile loads the state of the server when you expand it. It never shows server paths.
- The lines about the state of the server. Each has a dot: green for OK, yellow for a note, red for an error, grey for not measurable.
- A yellow line, here the functions that the hosting provider has disabled.
- Copy report copies the support report to the clipboard.
- Download report downloads the support report as a text file.
- The note says that nothing is sent automatically.
| Line | Shows | Yellow, red or grey |
|---|---|---|
| PHP version | The version of PHP. | red below PHP 7.4. |
| Database server | MySQL or MariaDB with the version. | yellow for another database server. |
| WordPress version | The version of WordPress. | Always green. |
| Plugin version | The version of cloneworx Backup. | Always green. |
| PHP extensions | Of the seven extensions that the plugin needs or recommends, the loaded ones; the line lists missing ones by name. | red if zlib or mysqli is missing. yellow if sodium, curl, mbstring, openssl or gmp is missing. The line shows such an extension with recommended but missing: …. |
| Folder permissions | writable if the plugin can create and write to its work folder and its log folder. If one of the folders is missing, the check creates it. | red with the reason. |
| Disabled functions | Functions of PHP that the hosting provider has disabled and that the plugin uses; otherwise none. | yellow as soon as one is disabled. |
| Memory limit | The memory limit of PHP or unlimited. | yellow below 64 MB. |
| Time limit | The time limit of PHP in seconds or unlimited. | yellow with the addition set_time_limit is disabled; steps end by time on their own. |
| Free space (work folder) | The free space where the plugin writes its work files. | yellow below 256 MB. grey with not measurable. |
The line Folder permissions shows one of these reasons:
- The uploads directory of WordPress is not available.
- The uploads directory is not writable.
- The plugin could not create its folder in the uploads directory.
- This server offers no secure source of random numbers.
- The database did not accept the code of this installation.
The line shows any other reason as not usable (…); the brackets contain an English code for the reason.
The support report
The report is plain text for a request to support. It has the sections website, server, plugin, settings, operation, targets, plans, jobs (the last ten), scope, diagnosis and log (the last 40 lines of the global log). The headings and lines in the report are in English.
What the report does not contain
The report contains no job names and no other IDs of backups, no names of targets and plans, no locations and credentials of the targets, no email addresses and no server paths. Targets are listed with ID, target type and state, plans with ID and their settings, email addresses only as a number. The address of the website is in the report. The plugin never sends the report itself. Check it before you pass it on.
The file is called cloneworx-backup-report_<host>_<date>_<time>.txt. If your browser does not allow access to the clipboard, Copy report also saves the report as a file.
Diagnosis
In the Extended view, the block Diagnosis is below the buttons of the report. None of the four diagnoses creates a backup.
- Probe run measures the server: how long a step can run, which task sources arrive, how much the work folder writes per second and how much memory is available.
- Run starts the diagnosis of the line.
- File list determines what a backup would contain and whether the space in the work folder and at the targets is sufficient.
- Database export exports the database into the work folder, reads the export back and checks it.
- Files dry run writes the file part of a backup into the work folder, without a target.
- After every name is the last run with time, result and key figures, or never run. For File list the key figures read … entries (… files, … folders), …; … excluded, … vanished; space: … and for Database export … tables, … rows, … raw, … stored in … parts, read back …, … s. For Files dry run they show entries, raw and stored size with the share in percent, parts, warnings, duration and space.
- The dot is green after a run without findings, yellow after a run with warnings, red after an error or abort and grey as long as the diagnosis has never run. While a diagnosis is running, a ring spins at its line.
- After the start the page reports … started. Below the block the progress display appears; Abort diagnostic run in it aborts the diagnosis; for the probe run the link is called Abort probe run.
- At the end the page reports … finished. or … ended with an error: … A yellow or red message takes you to the log of the diagnosis with Log.
- Only one job runs at a time. As long as one is running, the buttons are blocked.
- The results are also in the support report.
More on this: Get help: support report, troubleshooting and diagnostics.
PROBackup encryption
This feature belongs to cloneworx Backup Pro: Installation · Order
The tile sets up the recovery key for encrypted backups and is in both views. Only once the recovery key is set up can a plan encrypt its backups. You switch on the encryption itself in the plan, with Encrypt backups. Without cloneworx Backup Pro the tile shows only the Pro marker.
- The sentence explains what the tile is for.
- No recovery key is set up yet. Until then no plan encrypts.
- Set up creates the recovery key.
| The tile shows | Meaning |
|---|---|
| A plan can encrypt its backups for all its targets. An encrypted backup can only be opened with the key of this website or with the recovery key. | The sentence is always at the top of the tile. |
| No recovery key is set up yet. Until then no plan encrypts. | Set up creates the recovery key and shows it once. |
| Recovery key set up on …. | Plans can encrypt their backups. New recovery key creates another recovery key. Earlier backups can still be opened only with the previous recovery key. |
| A recovery key was created but not confirmed. Set it up again to get a new one. | Yellow. The setup was ended before the confirmation. |
| Strict mode is on: this website cannot open its new backups itself. | Yellow. Strict mode can only be switched on the command line. |
| The PHP extension sodium is missing on this server; backups cannot be encrypted here. | Red. Ask your host to enable the PHP extension sodium. |
| The key of the stored credentials is missing or cannot be read (Settings → Key); the backup encryption needs it. | Red. The Key tile names the reason. |
| The licence of cloneworx Backup Pro is not valid. Plans that encrypt their backups do not run until it is valid again. | Red. During this time a plan with encryption writes nothing, not even an unencrypted backup. |
Step by step: Encrypt backups.
Key
The plugin stores the passwords and keys of the targets encrypted, with a key of its own. It creates this key once when it starts and stores it in the database. There the key is itself encrypted with the security keys of the website from wp-config.php: with the constant CLONEWORX_BACKUP_KEY if it is set there, otherwise with LOGGED_IN_KEY and LOGGED_IN_SALT. The plugin writes nothing to the disk for this, and the database alone does not reveal the key, so neither does a backup. The tile shows what protects the key and is in both views.
- The passwords of the targets are encrypted with a key of their own. It is kept in the database, protected by the security keys LOGGED_IN_KEY and LOGGED_IN_SALT in wp-config.php; nothing is written to the disk. If those two values change, the stored passwords cannot be read any more.
- Renew key creates a new key and re-encrypts all stored passwords with it.
| The tile shows | Meaning | Button |
|---|---|---|
| The passwords of the targets are encrypted with a key of their own. It is kept in the database, protected by the security keys LOGGED_IN_KEY and LOGGED_IN_SALT in wp-config.php; nothing is written to the disk. If those two values change, the stored passwords cannot be read any more. | The key is protected by LOGGED_IN_KEY and LOGGED_IN_SALT from wp-config.php. If these values change, the stored passwords can no longer be read. |
Renew key |
| The passwords of the targets are encrypted with a key of their own. It is kept in the database, protected by the constant CLONEWORX_BACKUP_KEY in wp-config.php; nothing is written to the disk. If that constant changes, the stored passwords cannot be read any more. | The constant CLONEWORX_BACKUP_KEY is set in wp-config.php. It protects the key instead of LOGGED_IN_KEY and LOGGED_IN_SALT. |
Renew key |
| The passwords of the targets cannot be encrypted: libsodium is missing. | The plugin cannot encrypt any passwords. | none |
| The passwords of the targets cannot be encrypted: wp-config.php has no usable LOGGED_IN_KEY and LOGGED_IN_SALT (missing, empty or the sample value) and no CLONEWORX_BACKUP_KEY. Set them, then save the passwords of the targets. | The plugin cannot encrypt any passwords until wp-config.php has usable values. | none |
Renewing the key
Renew key opens the dialog window Renew the key?.
- A new key is created and all stored passwords are re-encrypted with it. The passwords at the targets stay the same. After a security incident it is strongly recommended to change them at the targets as well.
- Cancel closes the dialog window without changing anything.
- Renew key renews the key.
Afterwards the page reports Key renewed. The passwords at the targets stay the same. The renewal only protects what is stored afterwards.
The key of this website for encrypted backups is protected by the same key. When you renew the key, the plugin re-encrypts it as well. If the key cannot be read, renewing also drops the key of this website for encrypted backups: new backups get a new one, and earlier encrypted backups can then be opened only with the recovery key. More about this: Encrypt backups.
If a target reports the catalog of another website, the tile reads in yellow: This website looks like a copy of another one (a target reports the catalog of a different website). Renew the key so the copy does not share it with the original.
If the key cannot be read
If the security keys in wp-config.php or the constant CLONEWORX_BACKUP_KEY have changed since the passwords were stored, the key cannot be read. The targets with stored passwords then count as disconnected, and the tile reads in red: The key cannot be read: the security keys in wp-config.php (or CLONEWORX_BACKUP_KEY) have changed since the passwords were stored. Enter the passwords of the targets again, or renew the key. The dialog window Renew the key? then additionally shows in red: The key cannot be read. With the renewal the stored passwords of … targets are lost and must be entered again. After the renewal the page reports in yellow Key renewed. The stored passwords of … targets must be entered again.
As long as there is no readable key, the form of a target stores no passwords. The form then reads Passwords cannot be stored right now: there is no readable key (Settings → Key). How to enter the passwords of a target again: Renew the credentials of a target.
If individual stored passwords cannot be read with any key, the tile reads in red … stored passwords cannot be read with any key. Enter them again in the targets.
If the renewal fails, a red message shows the reason: Renewing failed: … Reasons are wp-config.php has no usable LOGGED_IN_KEY and LOGGED_IN_SALT and no CLONEWORX_BACKUP_KEY, a stored password cannot be read with any key; nothing was changed, no random numbers available and the re-encrypted passwords could not be stored.
Licenses
The tile lists the plugin itself first and, below it, the bundled third-party components. Every line shows name, version and license; License text opens the text of the license in a new tab. The license texts are included with the plugin. There is nothing to set here.
Uninstall
The tile has one switch: When the plugin is deleted, remove all settings and the index. Backups are kept. The default is off. The switch takes effect when you delete the plugin in the plugin list of WordPress, not when you deactivate it. As long as the rollback of a restore is open, the plugin cannot be deactivated and therefore cannot be deleted. If the switch is on at that point, the text below it reads in red: A restore still has an open way back. Decide with Keep or Undo before deleting the plugin: with this switch on, the previous state (old tables and folders) would stay behind and nothing could keep, undo or even find it any more.
| Switch | What deleting the plugin removes |
|---|---|
| off | The scheduled tasks of the plugin in WP-Cron and the work folder, which contains only leftovers. Everything stays in the database: a new installation finds settings, targets, plans and the list of backups again. The plugin does not revoke any access with a provider. |
| on | In addition, all settings and plans, the list of backups (the index), the configured targets with their encrypted credentials, the folder of the logs and the folder of the files that WP-CLI wrote with --to. Before that, the plugin asks Dropbox to revoke the access of every target of the type Dropbox. |
If the revocation at Dropbox does not succeed, the deletion is still completed. The access then stays valid at Dropbox until you disconnect the app in your Dropbox account. The plugin revokes nothing at Google, not even when it is deleted.
Backups are always kept
Deleting the plugin does not touch any backup, neither in the uploads directory nor at a local or external target, no matter how the switch is set. The previous state of a restore that can still be undone stays as well.
More on this: Uninstall the plugin.
See also
- Set up email notifications
- Start backups on time: set up a system cron
- Adapt the plugin to your server
- Get help: support report, troubleshooting and diagnostics
- Settings and scope with WP-CLI
On the command line
WP-CLI not set up yet? How to install WP-CLI.
Everything you set on this page can also be set with WP-CLI, plus test email, schedule, logs and support report. The output of the commands is in English. All keys of the settings are listed in Settings and scope with WP-CLI. Test email, debugging, logs and support report are described in State, logs and support with WP-CLI.
# Show all settings with their values wp cloneworx-backup settings list # Set the maximum per step to 10 seconds wp cloneworx-backup settings set step_max_seconds 10 # Show the exclusion rules wp cloneworx-backup scope exclusions # Send a test email to the recipients wp cloneworx-backup notify test # Show the schedule with the last tick wp cloneworx-backup scheduler status # Show what protects the key of the credentials wp cloneworx-backup key status # Enable debugging for 24 hours wp cloneworx-backup debug on # List the log files wp cloneworx-backup logs # Print the support report wp cloneworx-backup support