Hello,
I've upgrade my esx to ESXi-6.0.0-20160302001 profile and when I go to : http://host.dom/ui/ I get a '404 Not Found" page.
Thanks for your help,
can you try to restart service
#/etc/init.d/rhttpproxy restart ( or stop/start)
then try to access URL.
My configuration -
# cat /etc/vmware/rhttpproxy/endpoints.conf
/ local 8309 redirect allow
/sdk local 8307 redirect allow
/client/clients.xml local 8309 allow allow
/vpxa local 8089 reject allow
/mob namedpipe /var/run/vmware/proxy-mob redirect allow
/wsman local 8889 redirect allow
/sdkTunnel namedpipetunnel /var/run/vmware/proxy-sdk-tunnel allow reject
/ha-nfc local 12001 allow allow
/nfc local 12000 allow allow
/folder local 8309 redirect allow
/host local 8309 redirect allow
/tmp local 8309 redirect allow
/screen local 8309 redirect allow
/guestFile local 8309 redirect allow
/cgi-bin local 8309 redirect allow
/vvold local 8090 allow allow
/ticket tickettunnel /var/run/vmware/ticket/%1 redirect allow
Try to match this file, restart proxy service again and try to access URL.
if still this don't work, uninstall esx-ui VIB and install it, then try to access URL.
Thanks,
Haridas
have you upgraded ESXi fro prior version?
Try this
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
New HTML5 Embedded Host Client for ESXi | virtuallyGhetto
Yes, I have upgrade from 5.5U2 to 6.0.0 to 6.0U2 and I have looked at the file /etc/vmware/rhttpproxy/endpoints.conf but there was no line like "/ui local 8308 redirect allow" in it.
In My lab, I upgrade ESXi 5.5 to ESXi 6 u2 and https://esxi-hostname/ui worked without any issue.
Enable ESXi shell or ssh and login to esxi with root/password to run below commands
can you check if esx-ui VIB is installed on your system or not?
esxcli software vib list | grep -i esx-ui
this will print vib name, version...etc. if you don't get any output means esxi-UI vib is not installed and you need to install it manually.
IF esx-vib is installed, then check if rhttpproxy service is running or not?
/etc/init.d/rhttpproxy status
if output don't say http reverse proxy is running then you can try to start http service.
/etc/init.d/rhttpproxy start.
if you still get error, please share complete error message.
Check log file for errors #more /var/log/rhttpproxy.log
Thanks,
Haridas
I've :
esxcli software vib list | grep -i esx-ui
-> esx-ui 1.0.0-3617585 VMware VMwareCertified 2016-04-20
/etc/init.d/rhttpproxy status
-> VMware HTTP reverse proxy is running
in the /var/log/rhttpproxy.log
-> URL namespace /ui does not match any server namespace
maybe the log will ring some bells to you ..
Thks
can you try to restart service
#/etc/init.d/rhttpproxy restart ( or stop/start)
then try to access URL.
My configuration -
# cat /etc/vmware/rhttpproxy/endpoints.conf
/ local 8309 redirect allow
/sdk local 8307 redirect allow
/client/clients.xml local 8309 allow allow
/vpxa local 8089 reject allow
/mob namedpipe /var/run/vmware/proxy-mob redirect allow
/wsman local 8889 redirect allow
/sdkTunnel namedpipetunnel /var/run/vmware/proxy-sdk-tunnel allow reject
/ha-nfc local 12001 allow allow
/nfc local 12000 allow allow
/folder local 8309 redirect allow
/host local 8309 redirect allow
/tmp local 8309 redirect allow
/screen local 8309 redirect allow
/guestFile local 8309 redirect allow
/cgi-bin local 8309 redirect allow
/vvold local 8090 allow allow
/ticket tickettunnel /var/run/vmware/ticket/%1 redirect allow
Try to match this file, restart proxy service again and try to access URL.
if still this don't work, uninstall esx-ui VIB and install it, then try to access URL.
Thanks,
Haridas
Good news,
I've add the line :
/ local 8309 redirect allow
and restart the service
And I can acces the html5 web ui
Don' know why I didn't have this line. Maybe it was some restriction inside my original kickstart but I havn't locate it yet.
Thks for your help
Good to know it worked.
Please consider awarding points for "Correct" or "Helpful" replies. Thanks....!!!
Missing the / line in the reverse proxy is going to cause a bunch of issues related to loading of content from the host.
It's odd that it was missing, but this is the only case I have seen of this happening.
I'm glad you were able to sort it out!