VMware Cloud Community
asp24
Enthusiast
Enthusiast

connect to vc ui using domain name

I'm trying to access the virtualcenter ui from home using vc.domain.com (pointing to my public vc ip address)

The problem is that the UI login is expecting a machine name and complains about not finding http://vc/ui

When I add a entri in the hosts file, pointing vc to the ip address, everything works

Is it possible to change something to make this work? The virtualcenter server is not a part of a domain, but I have added "domain.com" as domain suffix..

0 Kudos
7 Replies
sbeaver
Leadership
Leadership

Do you have it listed in the DNS server that is the one used when you are home>?

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
0 Kudos
asp24
Enthusiast
Enthusiast

Yes, it IS listed. I can connect to http://vc.comain.com , but when I click on "log in to web access", the address changes to http://vc (the servername is vc). So it redirects to the hostname and not the full domain name..

It SHOULD be https://vc.domain.com/ui but it is https://vc/ui

0 Kudos
BMMGaucho
Contributor
Contributor

I am having the same issue - did you ever find a resolution without editing host files?

0 Kudos
bryanard
Contributor
Contributor

Has anyone found a solution to this?

0 Kudos
bggb29
Expert
Expert

try using the serverername with ui/ after it that shoud do it

i/e vcenter.mydomain.com/ui/

then bookmark it like this it should work properly.

Do you have a list of domain prefixes to search on your system. You can do that with OS X or windooz.

0 Kudos
bggb29
Expert
Expert

forget as stated above https://vcenter.mydomain.com/ui/

0 Kudos
saunders
Contributor
Contributor

You only seem to get this behavior when you are on the local machine trying it.

If you try it from a "client" machine on a different ip/subnet, it seems to get the FQDN working just fine.

Saunders

0 Kudos