Submitted by kstaken on Sat, 07/14/2007 - 12:07am.
If it's getting a self assigned IP there is something else that's wrong. The current JumpBox toolset is really geared toward running applications for internal usage. You can deploy them publicly, but it's more work than we would like and the value of a JumpBox in that scenario isn't yet where we want it to be. We'll be addressing this in the next major platform revision.
Does the IP start with 169? If so that is a self assigned IP and you probably won't be able to contact it. JumpBoxes currently require a DHCP assigned IP address. If it doesn't have one you won't be able to easily set it up.
Drupal IP is not usable
If it's getting a self assigned IP there is something else that's wrong. The current JumpBox toolset is really geared toward running applications for internal usage. You can deploy them publicly, but it's more work than we would like and the value of a JumpBox in that scenario isn't yet where we want it to be. We'll be addressing this in the next major platform revision.
Drupal IP is not usable
Thanks, what good is it if you can not access it? How can I set up a Drupal site and then turn on to the net?
Am I missing something?
Drupal IP is not usable
Does the IP start with 169? If so that is a self assigned IP and you probably won't be able to contact it. JumpBoxes currently require a DHCP assigned IP address. If it doesn't have one you won't be able to easily set it up.
Austin
Drupal IP is not usable
Hi, I loaded the .vmx file into vm server and all went OK until I was given the ip and mgmt ip. I tried logging into this ip and no good.
this VM has its own ip. I would like to configure Drupal to use this. Any advice please?
JR