I fooled around for a day trying to fix that it seemed to be unable to find the network no matter what I did. Finally, I got frustrated and "Ctrl C"ed to the prompt and logged in as root.
Every appears to be there but no desktop, I am connected to the network and OwnCloud is installed and works more or less.
So the question is what do I do. I intend to run headless using ssh and if I can get a desktop I want to use VNC for communication.
I want to use the Bootstrap plugin for adding a theme to Vanilla (supported) but it requires version 2.1.x. My AWS subscription says I'm version 13 - which doesn't seem to be the same version family.
What version am I, and since I realize I'm probably not 2.1.x - how can I upgrade my subscription to that?
I'm testing my restore procedure, and for the first time ever using an AWS cloudserver, via the HUB. Almost 24 hrs later now. Seems the restore has been done. I see files from the backup, not sure if it's 100%.
But in top, tklbam-restore is still hugging all available cpu. tail /var/log/tklbam-restore doesn't show any new progress.
What is keeping it busy and why? How can I find out more on what is happening?
I had a small issue with ProjectPier. I downloaded the ISO file and installed it on a local virtual machine. After the initial TKL configuration screens, I tried to access ProjectPier via a browser. The browser displayed the following error message:
Hi all, I've stumbled my way through setting up a moodle deployment, but have ended up with two AWS instances, a micro and a small, I'm almost certain that I only want a small, but both DNS point to the same active moodle location.. thoughts?
Also, what setting do I need to attack to enable https? THe site is giving new users the warning about it being unsecure in chrome.
I have installed the turnkeylinux PostgreSQL appliance on a Virtualbox VM. The installation default was to install with NAT but I was unable to SSH nor get to the various tools via the web from my Windows host. I then changed the networking interface to bridged
This might just belong over in the bug tracker bug I figured I should start here. I'm trying to build some of the 14.0 appliances and have been successful with a few (core, LAMP) but I'm running into problems with etherpad. TL;DR the install script for node.js seems to be broken (yes, I did do the git pull in common). My attempt to fix it is below but etherpad-lite eventually complains that it's not the right version of node.js
It does okay until it starts running the nodejs-install common script. Then I get this: