i hat a running t1.micro instance which I choosed to change to a m1.small instance, I did this, not thinking too long about it, by using the amazon aws console (stop instance, change instance type, start instance).
now the instance correctly starts up as a m1.small instance, however in the tk hub it is still shown as "t1.micro".
is there any way to update the metadata in the tk hub so that it shows the correct instance type there as well?
I fairly new to linux so this is just a brainfart on my part. How do I run the /usr/local/bin/zimbra-conf script to change the domain? I've dropped back to the console but I can't see to get it. I can't find other documentation other than "Run the /usr/local/bin/zimbra-conf script".
This is Not Current Version - Need to Update to VTiger 5.4
Hello,
I went into Amazon AWS Marketplace and installed AMI: turnkey-vtiger-11.3-lucid-x86.ebs_2-0a31614b-5e87-4b66-990a-b40f6859b866-ami-6e37eb07.1 (ami-1557887c) this morning.
But, it turns out that Vtiger that is included is not the latest version! So I stopped the instance and I need you to tell me how to update to VTiger 5.4.
I recently started using the Turnkey Hub as a way to host virutual machines we use locally as dev boxes. Rather than waiting around for my bosses to approve it, I created an account with my own credit card, and they are going to reimburse me for the charges so far... but they now want their own account seperate from mine.
This morning I cloned a Turnkey VM and it went no problem. Networking was set up to eth1, I assigned an IP and all was peachy.
I went through the same process aftr that cloning the new machine to a new third machine. All seemed to go well, but when I start the VM it is looking for ETH2 rather than ETH1. As such I can't log into it though I can kill the Console interface and root around there.
Why is this one looking for Networking on eth2 rather than eth1? I only have one Network Interface defined for the VM (and the same for the other VM's)
I haven't been able to connect to my VPN, recently and did some investigating. If I check my HubDNS account my tklapp.com address is correctly being displayed as my router's WAN IP address. What's weird is if I ping my tklapp.com address, it returns an IP address that according to WHOIS, is an Amazon ECS address. Any ideas...?
Thanks.
Drew
PS: Just for the hell of it, I changed my VPN client configuration to point to my router's WAN IP address and it connected right away. So this really is a DDNS not working.
I am having trouble with the "Limit to possible list" feature and I was wondering if I could get some guidance, I am fairly new to Samba configurations and I feel as though I've done everything logically, but still no joy.
My requirements are as follows for three different types of shares: