Brandon C

Hi Andrew

The 524 Error is produced by Cloudflare and it can be quite troublesome. A 524 error indicates that Cloudflare made a successful TCP connection to the origin web server, but the origin did not reply with an HTTP response before the connection timed out. There a few different ways to correct this error. Here’s a guide directly from Cloudflare support on how to diagnose and troubleshoot the 524 error.

Are you restoring a backup, creating a backup, or transferring a backup?  Total Upkeep is meant to make self-contained backups for disaster recovery or even migration, (by default) the plugin backs up the entire site.

The type of backup that you are speaking of is normally referred to as an incremental or partial backup. Incremental backups are being road-mapped for release in a future version of Total Upkeep, but they are unavailable at the moment.

From what you described it sounds like your backup file could be too large to transfer in the maximum time for the Cloudflare connection. A common cause of this is simply having a lot of media uploads. You may consider excluding your wp-content/uploads directory from your regular backups, and back up your uploads folder manually less frequently (maybe twice a month).

Judging from the size of your website and how quickly it is growing you may want to look into enterprise backup solutions from your hosting provider.

It’s also possible that we can help you identify some methods to keeps your backup size down from the information in your logs. In the lasted version of Total Upkeep, large files are logged for troubleshooting. Enable file-list analysis will allow you to see what parts of the backup are taking up the most space

Once you identify larger files simply navigate to Total Upkeep > Tools > Logs and look for the file starting with archive- that corresponds to your most recent backup. Copy and paste that here, and we’ll be able to see if the plugin has detected any large files you might be able to exclude from your backups or even delete if you don’t need them.

Hi Terry,

To fix the “insecure” warning and triangle, you’ll need to set up an SSL certificate with your hosting provider.

Since you’re using one of our Platinum WordPress Hosting partners, InMotion Hosting, you can set up their Free AutoSSL to fix this problem. Here are InMotion’s Instructions on how to set up a free SSL certificate.

In regards to the error message you are receiving I believe it’s being caused by a permalink issue. When I click on your homepage I see /home/home/home attached to the url which indicates a permalink error.

I’d suggest navigating to Settings > Reading and double-check that the setting for Your homepage displays is set to Home.

After double -checking your homepage URL navigate to Settings > Permalinks and make sure that you have the correct permalink structure selected. For example, choose Post Name instead of a Custom Structure.

If that’s already correct, use these instructions to refresh the permalinks.