1 2 Previous Next 20 Replies Latest reply on Feb 9, 2019 4:09 AM by TryllZ Go to original post
      • 15. Re: Can't access the vCSA via Web UI from host, cant get Stage 2 started..
        TryllZ Novice

        Yes the host can ping and SSH into the vCSA only the web UI can't be accessed through the host browser.

         

        So now I can access the address 192.168.10.12:443 but when I click the HTML5 window it does not find the IP.

         

        This site can’t be reached

        vcsa.dc.local’s server IP address could not be found.

         

        What I have noted is that once I click HTML 5 the browser just nearly opens up the SSO sign page before saying the address cannot befound

        • 16. Re: Can't access the vCSA via Web UI from host, cant get Stage 2 started..
          sk84 Expert
          vExpert

          This site can’t be reached

          vcsa.dc.local’s server IP address could not be found.

          Where does this "vcsa.dc.local" come from? I thought the FQDN was vcsa.vdns.local?

           

          And if you configure your vCenter with DNS and FQDNs, the corresponding DNS servers must be accessible by the clients. Especially if it is a .local zone that is not publicly resolved. If your laptop is using the Google DNS server, there will be problems. Or if vCenter cannot resolve these FQDN because the DNS servers for these entries are not reachable.

           

          This is especially true during deployment, but also later during operation. Alternatively, you can deploy vCenter only with IP addresses instead of a resolvable FQDN and configure the ESXi hosts also with IP addresses instead of FQDNs. In this case DNS is not so important, but you will never be able to change the IP address of the vCenter in that case.

          • 17. Re: Can't access the vCSA via Web UI from host, cant get Stage 2 started..
            a.p. Guru
            vExpertUser ModeratorsCommunity Warriors

            Nice, with this reply we now have tree disfferent names, vcsa.dc.local, vcsa.ad.local, and vCsa.vdns.local ;-)))

             

            Anyway, what you may do on the host system is to add an entry to the hosts file, so that the name resolution works.

            192.168.10.12     vcsa.<whatever-your.-domain-is>.local

            In Windows the hosts file can be found at C:\Windows\System32\drivers\etc. Make sure you add an empty line at the end of the file.

             

            André

            • 18. Re: Can't access the vCSA via Web UI from host, cant get Stage 2 started..
              sk84 Expert
              vExpert

              Anyway, what you may do on the host system is to add an entry to the hosts file, so that the name resolution works.

              Do you recommend that for a production setup?

               

              One more thing: You need to set this hosts file entry on each client from which you want to access the vCenter.

              • 19. Re: Can't access the vCSA via Web UI from host, cant get Stage 2 started..
                TryllZ Novice

                OK, so for the FQDN changing thats because I was working on a DC named ad.local thus vcsa.ad.local, then I was testing on a DC named dc.local thus vcsa.dc.local, sorry for the confusion.

                 

                The google DNS is obtained from DHCP, I have not set it manually, plus I am accessing ESXi via my host broweser, so no issues there, currently the issue is that I can access the 192.168.10.12 via browser, but when I try and click on the HTML5 for SSO sign in it says address NOT found.

                 

                When setting up vCSA I had used both FQDN and IP, I understand FQDN was optional, I used it nevertheless.

                 

                I tried a deployment with just IP address, same problem, the host cannot access the vCSA when installed in Windows server, I tried a deployment with vCSA installed on ESXi with AD, did not work., same problem, I tried a deployment y importing the vCSA directly into Workstation, same problem, can ping, can SSH but can't open from host browser.

                 

                I could use the host file method, but I understand your point of this approach in a production environment.

                • 20. Re: Can't access the vCSA via Web UI from host, cant get Stage 2 started..
                  TryllZ Novice

                  I finally got it working as follows (partly).

                   

                  But here is how I configured it.

                   

                  I only filled in the Network Configuration part and imported.

                   

                  I have an AD DNS server with A and PTR records added before importing.

                   

                  I have NOT used any FQDN, only IP addresses.

                   

                  And soon as the import finished, I changed the network mode.

                   

                  Currently I'm accessing the vCSA via another VM and NOT through host browser, not sure if it is suppose to be this way, my assumption is that since ESXi can be done this way so should vCSA, I could be wrong though.

                   

                  Thank You all.

                  1 2 Previous Next