Home > Blogs > VMware vSphere Blog

Can’t connect to the vCloud Director 5.1 Virtual Appliance? Try this…

It’s come to our attention that some folks may be having an issue after they deploy the vCloud Director 5.1 Appliance where they are unable to connect to the vCloud Director user interface or find that they can not connect to a remote console for the deployed VMs.  While we are still investigating the root cause of this issue, the following describes a fix that should help you get up and running.

To begin, first log into the vCloud Director console. Remember that by default in the vCloud Director 5.1 Appliance, the username is root and the password is vmware for accessing the console. Using a text editor, such as vi, edit the /etc/sysctl.conf file. For example:

# vi /etc/sysctl.conf

Find the line for net.ipv4.conf.all.rp_filter and change the value from a 1 to a 0.

Save the file and then run the command:

# sysctl –p

Then try again to access the vCloud Director Appliance through your web browser or connect to the console of a deployed VM.  You should be presented with the vCloud Director user interface or console, as expected.

The reason for this change is documented here (http://www.novell.com/support/kb/doc.php?id=7007649).  You’ll also note that you can set this attribute to a ‘2’, which may be more suitable in certain environments.

Again, investigation of this issue is still underway.  Once that concludes, there might be a different solution that is provided.

13 thoughts on “Can’t connect to the vCloud Director 5.1 Virtual Appliance? Try this…

  1. Jim Mece

    Have you seen anything similar in the non-virtual appliance install? I’m able to manage vcloud fine from the redhat box browser but i’m unable to authenticate from any other browser.
    Seperately I had to disable the rhel firewall to allow anything to even connect external to the rhel box.
    thanksd, JM

    1. Tom Stephens

      Not with this same issue. It sounds like it’s up and running on the local box, so it may just be a issue with the network connectivity.

  2. Matthew LeBlanc

    That fixed my issue, now is there anyway to redo the database connection to my MSSQL box? as it couldn’t talk to that network, it didn’t do anything with my database when it initialized for the first time.

    1. Tom Stephens

      Rerun the configure script (/opt/vmware/vcloud-director/bin/configure) by logging on through the console of the appliance (root/vmware by default) after you make sure that any failed DB instances are deleted.

      (Pg 25 of the VCD Install Docs can step you through this…)

      1. Jonathan

        If you re-run the configure script, you’ll have to provide the keystore location and password. Do you mind providing the password used in the 5.1/5.1.1 appliance? That is, unless, there is a way to bypass providing the keystore information when running the configure script.

  3. Jonathan

    I changed the appliance from dhcp to static
    I can login to the appliance and ping it

    I cannot connect to the VCD console htttp:///cloud OR https:///cloud

    On the appliance i verify that vcd-cell and vcd-watchdog are running using service …. status
    I also have a java process running /opt/vmware/vcloud-director
    nothing is listening on port 80 or 443 using netstat or telnet

    1. Tom Stephens

      You might need to generate new SSL keys for the http and console proxy IP addresses and run the configure script again if you happened to change the IP from what was picked up from DHCP.

  4. jim

    I cannot connect to the application interface even after making the console changes above (Find the line for net.ipv4.conf.all.rp_filter and change the value from a 1 to a 0) I can connect to the Administrator Inferface when using the same IP: http://xx.xx.xx.xx:5438 but when i click “Open Application” and it attempts to open a connection to http://xx.xx.xx.xx (no port defined but assume 80) i get an IE diagnose network issues… very frustrating.

    i am running the VCD as an appliance in a 5.1 environment (Evaluation Mode).

    Any Ideas???

    1. Tom StephensTom Stephens Post author

      Did you change IP addresses from what the vCD Appliance had the first time you booted it? If this happened (like say on first boot it got a IP address from DHCP and then you changed that to another address), then you might want to look at generating self-signed SSL certs for the http and console proxy.

  5. stefano

    I’ve the same issue.
    Deployed the appliance and the SQL DB setup didn’t complete as the appliance does not connect to network
    I tried changing to 0 the value as suggested but didn’t have any result
    I’m in the middle of evaluation the product but couldn’t because of the network issue

    1. Tom Stephens


      Did you try to rerun the configure script (/opt/vmware/vcloud-director/bin/configure) by logging on through the console of the appliance (root/vmware by default) and setting the IP information? Once you do that, I’d verify that you can ping the host and that it’s on the network. (You can do this while your still logged in to the vCD appliance). If you still can’t access it, then I’d try to regenerate some self signed SSL certificates and try again.

  6. IT Support Tulsa

    Talented technical support representatives are able to solve problems quickly and efficiently.
    There should be procedural guidelines for determining not only the skills,
    traits, and qualifications of the remote-based talent but also off the homke offide location and overall suitability to meet the company’s safety and efficiency requirements.
    That is why it is important to check out any company or individual who you are considering hiring, ask them to provide references and examples of their previous work
    if possible.

    Look at my blog; IT Support Tulsa

  7. Pingback: Can’t connect to vCloud Director UI? Try this! | Quak Quaks of the Ugly Duckling

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>