mdartez_he
Contributor
Contributor

ESXi Update 2 - Host UI - 503 Errors

Jump to solution

After Upgrading my host to 6.0 U2 today, I am getting 503 Errors:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0xffa014e8] _serverNamespace = /ui _isRedirect = false _port = 8308)

Not sure whats happening.  Ran the get command to see what version I was on to double check:

[root@ESX-LAB-03:~] esxcli software vib get -n esx-ui

VMware_bootbank_esx-ui_1.0.0-3617585

   Name: esx-ui

   Version: 1.0.0-3617585

   Type: bootbank

   Vendor: VMware

   Acceptance Level: VMwareCertified

   Summary: VMware Host Client

   Description: An embedded web UI for ESXi

   ReferenceURLs:

   Creation Date: 2016-03-03

   Depends: esx-version >= 5.0.0

   Conflicts:

   Replaces:

   Provides:

   Maintenance Mode Required: False

   Hardware Platforms Required:

   Live Install Allowed: True

   Live Remove Allowed: True

   Stateless Ready: True

   Overlay: False

   Tags:

   Payloads: esx-ui

Any ideas?

1 Solution

Accepted Solutions
SteveGalbincea
VMware Employee
VMware Employee

FIXED!

All you need to do is remove the '/ui' line from the '/etc/vmware/rhttpproxy/endpoints.conf' and restart rhttpproxy service by running '/etc/init.d/rhttpproxy restart'

Done!  Smiley Happy

View solution in original post

10 Replies
Techie01
Hot Shot
Hot Shot

Can you share the contents of /etc/vmware/rhttpproxy/endpoints.conf .

It could be due to the reason that you have customized the endpoints.conf file earlier and might have added an entry to /ui at port 8308 ( may be due to support http connection to MOB or SDK). Since the hostclient uses the /ui, the current entries in the file might be redirecting the connection to port 8308 . Seeing the endpoints.conf file will help to identify the source of the problem

0 Kudos
mdartez_he
Contributor
Contributor

/    local    8309    redirect    allow

/client/clients.xml    local    8309    allow    allow

/fdm    local    9089    reject    allow

/ha-nfc    local    12001    allow    allow

/mob    namedpipe    /var/run/vmware/proxy-mob    redirect    allow

/mobfdm    local    9090    redirect    allow

/nfc    local    12000    allow    allow

/sdk    local    8307    redirect    allow

/sdkTunnel    namedpipetunnel    /var/run/vmware/proxy-sdk-tunnel    allow    reject

/ui    local    8308    redirect    allow

/vpxa    local    8089    reject    allow

/wsman    local    8889    redirect    allow

Ok, so there it is above:

/ui    local    8308    redirect    allow

What should it actually be?

0 Kudos
SteveGalbincea
VMware Employee
VMware Employee

Same issue here. I did previously have the Fling for host client installed on these hosts, so that may be an issue.

Web UI message:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x1f0daf08] _serverNamespace = /ui _isRedirect = false _port = 8308)

cat /etc/vmware/rhttpproxy/endpoints.conf:

/    local    8309    redirect    allow

/cgi-bin    local    8309    redirect    allow

/client/clients.xml    local    8309    allow    allow

/fdm    local    9089    reject    allow

/folder    local    8309    redirect    allow

/guestFile    local    8309    redirect    allow

/ha-nfc    local    12001    allow    allow

/host    local    8309    redirect    allow

/mob    namedpipe    /var/run/vmware/proxy-mob    redirect    allow

/mobfdm    local    9090    redirect    allow

/nfc    local    12000    allow    allow

/screen    local    8309    redirect    allow

/sdk    local    8307    redirect    allow

/sdkTunnel    namedpipetunnel    /var/run/vmware/proxy-sdk-tunnel    allow    reject

/tmp    local    8309    redirect    allow

/ui    local    8308    redirect    allow

/vpxa    local    8089    reject    allow

/wsman    local    8889    redirect    allow

Thoughts?

0 Kudos
SteveGalbincea
VMware Employee
VMware Employee

For what it's worth, I tried uninstalling and reinstalling the .vib for the ESXi host client - no change in behavior.

0 Kudos
SteveGalbincea
VMware Employee
VMware Employee

FIXED!

All you need to do is remove the '/ui' line from the '/etc/vmware/rhttpproxy/endpoints.conf' and restart rhttpproxy service by running '/etc/init.d/rhttpproxy restart'

Done!  Smiley Happy

View solution in original post

vijayrana968
Virtuoso
Virtuoso
  1. Backup endpoints.conf first.
  2. Log on to your ESXi host (either via SSH or DCUI/ESXi Shell)
  3. Edit /etc/vmware/rhttpproxy/endpoints.conf
  4. Remove the line:
    /ui    local    8308    redirect    allow
  5. Now restart the rhttpproxy:
    /etc/init.d/rhttpproxy restart
  6. You should now be able to access the Host Client at https://[yourhost-ip-or-name]/ui/

Follow post : Host Client – Tech Llama

Please remember to mark the replies as helpful/answers if they help and un-mark them if they provide no help.

JimJonesWV
Contributor
Contributor

Yes, this is in the actual documentation for the fling. Verbage from the site is:

  • For ESXi 5.5U2 and prior, and ESXi 6.0 hosts upgraded from any 5.5U2 or prior version, you will get a 503 error returned after visiting https://<esxhost>/ui/. To resolve this issue, please remove the line starting with /ui from /etc/vmware/rhttpproxy/endpoints.conf and restart rhttpproxy with /etc/init.d/rhttpproxy restart
0 Kudos
SteveGalbincea
VMware Employee
VMware Employee

JimJonesWV Indeed it is - that's where I found the solution (about 5 minutes after I first replied)  Something...something...read the something manual, right? :smileylaugh:

0 Kudos
elesueur
VMware Employee
VMware Employee

Hmm, we should have probably included this in the Known issues section of the 6.0 U2 release notes. I will see about getting them updated.

0 Kudos
rajugupta
Contributor
Contributor

I also encountered exactly same problem but resolved this issue by following these steps:


- Loged into ESXi host using putty

- Open  /etc/vmware/rhttpproxy/endpoints.conf in editer

- Removed the line: /ui    local    8308    redirect    allow

- Restart the rhttpproxy: /etc/init.d/rhttpproxy restart

- Now Its working fine. Smiley Happy

0 Kudos