EB's picture


I have a vague understanding that TKLBAM is supposed to be used with AWS which eventually has a cost.

I'd like to explore the use of otherwise unused usb flash I have around here. I have very little content on my TKL Wordpress to backup but the configuration and appearance was time consuming and I'd like to preserve that as much as possible so that it can be easily restored at a later time if necessary.

Is there a way to do this automatically at certain times? Should the usb storage not be connected to the computer most of the time, to avoid potential for loss from hacking or other intentional destruction via network?

Welcoming thoughts and advice. Thank you.

Jeremy Davis's picture

Yes it's possible to backup to a USB (or any other local filesystem). Although personally, as per your note re "avoid potential for loss from hacking or other intentional destruction via network" it might be better to backup to some alternate network location?

Also regarding cost, if you only have one server to backup, then you could use the "backup free" Hub plan (if you wish to avoid Hub costs, be sure to downgrade to free plans before the 14 day free trial ends). Then you would only have AWS S3 storage costs. Considering that TKLBAM is a "smart backup" (so only stores the files it needs, rather than the whole OS) considering your use case, the backups will likely be tiny. You can also limit the number of full backups the Hub stores, so if your site is relatively static and you only keep a few months of backups, the costs would be minimal.

FWIW AWS S3 costs less than $0.03/GB/month so on a small WordPress site with 3 months of backups, it's likely that your annual costs would be less that $1/year! Although it's important to note that there may be other costs incloved with S3, such as data transfer. Please see the full AWS S3 pricing page for full details (although I'm sure the full price will still be more than reasonable).

If you still wish to persist with using a USB for your backups, then the TKLBAM FAQ may assist, specifically here and here.

It's also worth noting that your USB won't auto mount, you'll need to do that manually. But considering your desire to (possibly) not have it mounted all the time, perhaps that's a feature in your case? Regarding mounting and unmounting of the USB, you could edit the tklbam cron job to also take care of that if you wished, although it might be useful to include a test to ensure that it's mounted by the time that tklbam runs? An alternate path would be to instead create a TKLBAM hook script to mount/unmount the USB. The beauty of this second path is that you could then also have it mount/unmount when you wish to restore from your backup?

EB's picture

Because you are advocating heavily for AWS I will look at it some more. I looked at the AWS link you provided and this https://aws.amazon.com/free/?all-free-tier.sort-by=item.additionalFields.... Clearly much more reading is required.

Thank you

Jeremy Davis's picture

I'm primarily advocating for AWS because it "just works". Also having an offsite backup is definitely a desirable thing IMO.

Other options are totally legitimate, but will require much more engagement to get working.

EB's picture

Ok, I went through the directions. Looks like an anr was created on AWS and copy / pasted into TKL's interface at which point the instructions ended I was presented with what appears to be pay based service on TKL? Is that what I'm supposed to find? Thank you.

Jeremy Davis's picture

Please see the full details here. If you have any further concerns or questions, please do not hesitate to ask.

EB's picture

Ok. Thank you. I understand the creators of TKL would like to get some compensation for their time and efforts. :-)

I'm trying to get Let's Encrypt to work. I've been using TKL on an unused laptop. It's working fine but I want to make things more correct, including getting https working, a good backup solution, etc.

I tried the Let's Encrypt process over the weekend and again this evening. Errors resulted. Wondering if there is a network issue or anything that might be evident to you.


There is mention of errors in the days log file, but that path is not specified.

Images of the errors:


Thank you again.

Jeremy Davis's picture

Unfortunately, it's a known issue. FWIW, there are a few threads here on the forums which discuss it. The short answer (and the solution) is to update to a newer version of Dehydrated (the Let's Encrypt client we use on the backend), plus a newer version of Confconsole (to support the newer version of Dehydrated). The step-by-step instructions on how to do all that is covered in the Confconsole v1.1.2 release notes.

FWIW, Let's Encrypt changed things which broke Dehydrated. But the updated Dehydrated broke Confconsole in numerous different ways. But after a few false starts, if you follow the above procedure, you should be up and running in now time... :)

Add new comment