I have a turnkeylinux LAMP stack, and installed Jenkins on it. I moved Jenkins to port 80, and changed apache to port 8080. After doing so, the hyperlinks in the index.php page didn't work, because they showed up as https://server:8080:12320, instead of https://server:12320
The fix was super easy, just added a regex to strip off the existing colon and port number.
I have tried several times to Clone a new server from latest snapshot however the new server seems completely impervious to my attemps to either SSH or Webshell into it as required below. Hence I have no way of accessing the Snapshot. The console log all looks fine, nothing unexpected.
Anyone got any bright ideas of how to get it working?
Hi, I recently setup one of your WordPress instances @ AWS. Unfortunatley, because I was in the middle of a very active Skype session at the time, I accidentally closed the browser tab that contained my various admin/login settings :(
How do I retrieve all of this info at every level necessary (WP, LAMP, etc)?
Your rapid response would be much appreciated! Thanks.
Having a problem using Cyberduck (the latest versions both on a OSX Mac and on a Windows computer) to connect using the WebDav on port 443 to my TKL server. Both will connect no problem on port 22 for SFTP (using both the internal IP and the WAN connection, so I know that it is not a port forwarding issue-22, 443, 12320-1, etc. all properly forwarded).
at the moment I am trying to migrate a Joomla 1.5 installation to version 2.5 using jUpgrade. At first I want to test the migration process in a Turnkey Joomla installation with a local VMWare Player. But the migration process stops very early with the error message "406: cURL not loaded". The same error occurs when I run this installation on the Turnkey Hub.
Is there a way to enable cURL in a Turnkey Joomla 1.5 installation?
My main LAMP instance, managed with Turnkey Linux, was unreachable. Reboot didn't help. Stop didn't work properly and the instance was left in the stopping state for long time (hours).
I went to the AWS panel and tried a force stop. That didn't help either, so I started a new instance from AWS panel with a random 32 bit linux. Started it and turned it off, materialised last night's S3 snapshot as a volume and then switched the boot disk to use the just created volume. I booted it up, and associated the elastic IP.
I used webmin on my hub appliance to enable daily backups, however the backup rarely succeeds. (Rarely shows a backup session on the hub.) Yet if I run tklbam-backup at a command prompt it always works.
I have checked that the backup script in /etc/cron.daily is getting called. /var/log/tklbam-backup shows the date/time for each day, but many days it's only the date/time (and a bunch of hashes,) that gets logged.
The time shown for backup sessions on the hub doesn't look quite right. I made a number of backups over the space of an hour and the time for each of them shows 8 minutes past the hour (while those I made last month show 7 minutes past the hour.) Is it using the month instead of the minute?
Is there any other way to list backup sessions? tklbam-list shows backup profiles(?) but I can't see any way to list individual backups/sessions.
