Does Turnkey Lamp Stack Run its own Dns so other computers on the net can resolve the ip? Just like most webhosts running dns on the same server as where the websites are served.
I had 2 small LAMP instances running on TKL. I also have several websites on each. Once day, one of my customers said they couldn't reach their website. Lo and behold, one instance was listed as "Destroyed" on the Hub control panel! I had termination protection on both instances and yet one just disappeared!
Is there any way to find out what the heck happened? Luckily I was able to spin the instance back up from a backup, but I really want this to be resolved. Was this an AWS problem? Was this a Turnkey problem? Is there any way to know?
I wanted to ask if there is any way to applied a new API to a Turnkey Server instance which has already had the tklbam-init command activated with another API.
I'm attempting to work my way around the fact my account has unexplainably been unable to backup since August due to some Amazon-side stuff to do with my credit card (same card, same everything!).
I'm having an issue with the Fileserver Appliance (v12.0 Debian 6.0 squeeze) when mounting an NFS volume. I am hoping to use the Fileserver appliance to sit in front of an NFS volume to provide access to the volume over SCP.
Firstly, I found that I needed to install nfs-common & portmapper in order to initiate a mount -t nfs. I found the directions required to do that elsewhere.
I am confused. I set a billing alert to go off if my charges reached 5 dollars. On the TurnKey Hub it calculates one price, about $24 dollars. I thought, no sweat, when I view my Account Activity on Amazon it says around $4. Today I noticed in the fine print to check "View AMI Paid Activity." So I go there, and it says I'm going to be billed for $50??? This is outrageous, please tell me TurnKey isn't going to screw me over like that. Everything I saw said a lightly used hobby plan was free from both Amazon and TurnKey.
Hi there, loving TKL - I use several of your applications!
Having a slight issue with my latest endeavour though and was hoping somebody could help;
I'm running gitlab in a Hyper-V instance of server 2012 which already has an IIS server setup serving websites on port 80 and I have no idea where to even start on using IIS to deliver the pages from the gitlab instance so what I decided to do instead was change the listen port of gitlab.