I have set up a new account and I have three servers in total. I have run full backup on two them and they appear in S3 all good. The problem is the two servers are both using the same turnkey image ie Turnkey Postgres therefore in the backup control panel I have two identically labelled backups.
On the restore list in Webmin both backups are listed for each server even though they do not apply. I appreciate you need to be able to restore a backup to a new server but very easy to get confused when you have duplicate labels and you restore the wrong back up to the wrong server.
Hello, I've run into an issue with the TKL Fileserver App. I can create some shares that work just fine, and then there are shares that will not allow me access them despite having the same samba and linux permissions. Here's an example.
I've built three! Two on ESX 6.0 and one on Mac Fusion 8, and on none of them can I login to rtorrent interface or even admin with the password I input on install.
What exactly do I put in the web login screen for the ruTorrent area?
So it is a specific known problem with the nfs of your template?
I don't know why but only your template is unusable, every other vm or templates is working fine using the nfsclient but apparently not yours. Is it an old version or smething like that? I am always been denied from the service. : mount.nfs: access denied by server
and still the access is good and there is not firewall or things like that. so very stange
Is it a specific version of nfs which doesn't accept anonymous connection ?
I had a production server backing up every hour on tklbam.
Now, I take a previous snapshot of this server from my cloud account (not AWS), and restore from latest tklbam backup of the production server to get an exact copy (for development and testing).
First, the restore took so long that the new server backed up an increment to the existing backup on top of the production servers increments - I presume that messes up my chain, and I should force a full backup asap?
I ran an apt-dist upgrade and after a while, everything went according to plan, other than not being able to access webmin anymore. Sites all function properly, adminer and shell still function (at ports 12320 and 12322).
Any ideas what happened and can it be reversed or salvaged?
I have two Turnkey LAMP Stack OVA's - version 13 and version 14. I have a FRESH install of Wordpress, latest version on both VM's (Turnkey LAMP v. 13 & 14). Permalink %postname% works on version 13, but ont on version 14. Mod_rewrite is installed on both VM's. I'm stumped and can really use some advice.
These are fresh, vanilla installs of EVERYTHING. No special plugins, apache tweaks, nothing.
Permalink with default post number works on v. 14, but %postname% does not, which relies on mod_rewrite. The result is a HTTP 404 error on everying except the home page.