So I am assuming that will be of little use to you at this point. TKL appliances are basically headless servers and as such are designed so all admin can be done remotely (thus they include no fancy desktop environment, only commandline). To access/use/play with Magento you will need to use your web browser. On the confconsole screen (blue screen with plain text) it should tell you the IP to use. Alternatively you can set a static IP. If you have shut confconsole (sounds like you have) then you can start it again by typing confconsole at the commandline.

If you have any problems accessing it, double check that you have your virtual networking set to either 'host only' or 'bridged' (NAT won't work). If you wish to access your appliance from a machine on your LAN other than the VBox host machine, you will need to use 'bridged'.

As you will see from the confconsole, there are other ways to administer your appliance such as Webmin (Linux Admin WebUI), Webshell (Web based terminal/commandline access) and some have phpMyAdmin (WebUI for administration of MySQL daabases - although I'm not sure if Magento includes this one?) But as I said before you can also use Windows client software (such as Filezilla for filesystem GUI, or PuTTY for SSH/commandline access).

Adrian Moya originally developed this appliance and in his initial patch, he included a bash script to set the domain. I'm not sure whether the TKL devs kept that script or included that functionaily somewhere/somehow else.

You could just try running it like this first:

setupdomain DOMAINNAME

For example:

setupdomain www.example.com

If that doesn't work then I can only assume that the script isn't included. Adrian's original script is documented in his patch documentation here. Scroll down to the section titled "setupdomain script". If you copy/paste that into a text document (use nano inside your appliance or Notepad++ from Windows - don't use Win Notepad as it mangles Linux files), make it executable and run it in your appliance, it should work.

If you have further probs I'll try to help out but as I said I'm not familiar with Magento (although usually fairly handy with basic/generic Linux stuff and a dab hand with google!) As TKL appliances are usually a default install of the particular app, often the best place for specfic info re support are the app's documentation/wiki/forums/mailing lists/etc eg in this case Magento CE support area is probably a good starting point. Often google can provide lots of info too. If you do come across any problems (or even better still solutions) it'd be great if you can post them here. The theory being that if you encounter it, you can be sure that someone else will too. That is one of the best ways you can 'give back' to free open source software IMO.

Assuming you are using this as a devlopment server to be run as a VM and accessed via the host machine, then choose a domain and add an entry to the hosts file of the host machine pointing to the VM. Then everything should work as expected.

As for the other question (where to input commands) that's what PuTTY is for, or you can quit out of confconsole or use Webshell (https://xxx.xxx.xxx.xxx:12320) via your web browser.

Just add the domain name and the IP address of your VM (seperated by a space or tab from memory) to your hosts file and you should be good to go.

It's been a while but from memory, there is often an example entry in the hosts file of either localhost, or sometimes something random commented out. Try something like this:

myrandomfakedoamin.com   192.168.1.104

So we're on the same page here. I am talking about the hosts file in your host OS (ie Win 7). It should be C:\Windows\System32\drivers\etc\hosts or similar. I have also read that the only way to edit it in Win 7 (and Vista) is to open Notepad as Admin (right click - open as Admin) then browse to the file (even if your account has Admin privileges). Otherwise you will get an error when you go to save.

Let us know how you go. And any more questions, don't hesitate to ask.

Well actually I didn't test that specifically, but I tested the fileserver.py on the fileserver appliance and it worked like a charm. :)

Thanks Alon

[update] I have now also tested mysqlconf.py on the LAMP appliance and this works as well.

First things first - if you ping mage.com does 10.0.2.15 reply? If so you are good to go on that issue. 

If the above works, what happens when you browse to mage.com? What is displayed?

I'm not sure if magento supports top-level domains, you might need to specify a subdomain, for example: test.mage.com

BTW, if your appliance is accessible from the internet, you could use the free tklapp.com domain, in which case you wouldn't need to mess with your hosts file. It would also make it very easy to later migrate the server using the exact same fqdn to the cloud using tklbam.

VDI stands for Virtual Disk Image and it is in effect your VMs HDD. So that is where Magento is installed.

The second screenshot you gave is the Configuration Console (confconsole) and yes the IP there (10.0.2.15) is the one you'll use (in this instance - it's quite likely that will be different with a new VM). If you can't ping its IP from your host machine (while it's running - ie ping 10.0.2.15) then there is some other issue at play.

Double check you have set VirtualBox networking to either 'bridged' (which is probably the easiest although also the least secure way to go) or 'host only' (which will only allow you to connect from your host PC, no internet in or out). If you choose 'host only' you can add another virtual NIC (set to 'NAT') to give you internet access (for updates, backup etc) but perhaps don't worry about that just yet.

Once the appliance is installed and running and you have configured your static IP then you will no longer need to refer to that VirtualBox window (although you can use it for commandline stuff if you'd like). Personally I prefer to just use PuTTY and Filezilla (good for GUI filesystem management). Also everything can be done via your web browser. All the required info is displayed in the confconsole. Webshell is a web based CLI, Webmin is a Linux admin WebUI and phpMyAdmin is a MySQL database admin WebUI. Once you have the basics set up you only rarely need to use them. Most of your work will occur through the main web site.

Particularly: Reply from 98.xxx.xxx.1: Destination net unreachable.

I'm not sure why 98.xxx.xxx.1 is even trying to respond! Perhaps try a traceroute (ie tracert 10.0.2.15) to see where it is going. You could also try pinging your host machine from inside your VM (quit out of confconsole to get to the Linux CLI). The ping command works very similarly in Linux, only thing is that it will ping forever until you stop it (not just 4 times like WIndows) <Ctrl><C> to quit out of it.

Like I said above check the VM networking (accessed via the VBox GUI - config for your VM) - probably best to go with 'bridged' networking for now. You will need to shut down your VM to change it (otherwise the option will be grayed out). If it's currently set to 'NAT' then that's your issue - easy fixed! If your VM is still set to DHCP then it should auto refresh on boot. Otherwise try refreshing the IP (via DHCP). Easiest way to do that is to set it to static (any IP - probably best to set it to something odd so you'll know when DHCP has picked up a good IP), save, then set it back to DHCP - all done via the confconsole. Test you can ping it from your host and if so, set that same IP as static (via confconsole).

If it's already set to 'bridged' but still not working then you'll need to try to work out what the issue is - it shouldn't be anything to do with TKL, it'll be something with VBox or Windows. You could try to refresh the DHCP IP as I said in the above paragraph, but I doubt that'll do it.

Once you have a valid working IP I strongly suggest you set it to static.

To access your VM's filesystem I suggest you try Filezilla (SFTP). It is a dual pane Windows Commander style GUI for filesystem access (via SFTP). Webmin also has a (Java based) file manager.

There are other ways you can go, but as SFTP is setup and running by default it requires very little config to get going. Other SFTP options include WinSCP or there is an alpha SFTP Windows Explorer plugin which I found in my travels some time ago but haven't tested (sorry forget the name of it). You could also use Samba (Windows filesharing for Linux - you'll need to install it in your appliance) or Virtual Box shared folders (you'll need to install VBox tools - a little tricky). Both of these last options require additional config and as such I think you'd be better off leaving them alone at least for now (wait until you have this bit running and working as expected then explore other options if you're keen).

But obviously still not quite there yet.

As for whether it is an issue to post that detail publicly I don't think it's a problem (the only info that gives anything away is "adsl-98-xxx-xxx-1.bna.myisp.net [98.xxx.xxx.1]" but even that only denotes where you are connecting to (ie your ISP). [edited to remove info that may possibly be identifying]

Not sure what that error is about. As it says error reporting is not enabled by default. If you want to do some troubleshooting you'll need to enable error reporting. Some other have had similar issues, you can have a read here and here to perhaps get some ideas.

And sorry, no idea why you can only edit some posts. You should be able to edit all of your own posts. I'm a moderator here though so if you want me to edit something for you, send me a message (click my name and use the contact form) detailing which post (perhaps give the link to the post) and what you want edited.

Good luck with it all.