Web Access Broken if Custom Port Specified

A few customer are hitting a problem with Virtualcenter 2.5 when they use non-default ports for WebAccess.

There is a published KB article on there here: https://kb.vmware.com/kb/1003915

When you try to log in to VMware Virtual Infrastructure WebAccess when a custom HTTP port has been specified (whether during installation, before an upgrade, or after), the error “Web service unavailable” is shown.

By default VMware Virtual Infrastructure WebAccess uses port 80 when you connect. If a modification is made to the default HTTP port for VMware Virtual Infrastructure WebAccess, the configuration is not properly saved and the error above is noted when a user tries to connect. I have provided the  workaround to several customers on the phone and it has always worked.