Keywords: General - Virtual Machines - How to - Other
I've seen questions about the above error on multiple forums but none of them ever posted an answer. I thought I'd post the answer for posterity. I believe this applies generally to all Bitnami images.
The short answer is, this is a VirtualBox/VMWare configuration issue. Details of how to fix the configuration will depend on which product you are using.
By default, the Bitnami OVAs I've worked with all attempt to create a Bridged network. This puts the Virtual Machine on the same network as the host operating system and allows you to interact with it directly.
With my installation, the problem was selecting the correct NIC to use. On my version of Virtual Box, this was in Network->Adapter 1-> Name: I had five real and virtual NICs to choose from. The default choice was wrong. Try one of the others. If none of them work, it may be your host network is not allowing the VM to get an IP address. If this is true, Bridged Network will not work for you.
If you do not wish to (or can't) use a Bridged Adapter, you can also use (on VirtualBox) NAT, NAT Network and Host Only. For Host Only, you must open your Host Network Manager (in Global Tools). Either use one of the adapters already there, or create a new one. However, insure you select "Enable" for the DHCP Server for that adapater or your VM will not get an IP address. Again, with me, the default Adapter chosen did not have DHCP Enabled.
For NAT Network, you must first create the network. This is created in File->Preferences->Network->NAT Networks. You must enabled DHCP. If you wish to access the VM from your host operating system, you must also configure Port Forwarding. You can then select the network by name when you choose NAT Network as the network to attach to.
For NAT, you do pretty much the same thing except you do not have to create the NAT Network in advance. The Port Forwarding is in Advanced settings for the Adapter.
In theory, you should be able to use the Internal Network option as well as setting static IPs. However, I got bored and stopped playing with it.
In all cases, the source of the error was a failure to obtain an IP address. Any solution that gives the VM an IP address should work. All the other options just dictate how you access the services.