<

vCenter issue: vSphere Client fails with "Invalid URL: The hostname could not parsed."

Published on
4,185 Points
1,085 Views
1 Endorsement
Last Modified:
Luciano Patrão
VCP6.5-DCV, vSAN Specialist, vExpert last 3*, Veeam Vanguard. Expertises VMware, Virtual Backups and Storage design and a active Blogger.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed."

When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed."
 
001.jpg
The issue itself is described in VMware KB 1033990. Since there was no changes in the URL, was a strange issue.
 
There is some options to fix the issue. Since changing something in the ADM is not an option for many, we need to check the vCenter Advance Settings in VirtualCenter.VimApilurl or VirtualCenter.VimWebServicesUrl to check the error.
Since vSphere Client doesn't work to check the Advanced Settings, we need to use vSphere Web Client.
 

Procedure
In the vSphere Web Client, navigate to the vCenter Server instance.
1 Select the Manage tab.
2 Select Advanced Settings.
3 Click Edit.
 
004-768x315.jpg 
Then when the Advanced Settings board shows, just search(right upper corner for a quick find of the options we need to change) for the word "virtual" and then you will see the VirtualCenter.VimApilurl and VirtualCenter.VimWebServicesUrl options.
 
As you can see in our case both options were empty and the VirtualCenter.VimApilurl  have only "https://:443/sdk" when should have "https://vCenterFQDN:443/sdk" and VirtualCenter.VimWebServicesUrl is empty. But VirtualCenter.VimWebServicesUrl is optional.
 
003-768x543.jpg
We just need to add the vCenter FQDN into VirtualCenter.VimWebServicesUrl (https://vCenterFQDN:443/sdk), and in the VirtualCenter.VimWebServicesUrl (is needed, but not mandatory) and after this the issue is fix.
 Note: Share this article, if you think is worth sharing.

Hope this can help bypass this error in the future.
 
This article is the part of my "TIP Articles". So, please vote "Helpful" on this Article. And I encourage your comments and feedback.
1
Enjoy this complimentary article view.

Get unlimited access to our entire library of technical procedures, guides, and tutorials written by certified industry professionals.

Get 7 days free
Click here to view the full article

Using this article for work? Experts Exchange can benefit your whole team.

Learn More
COLLABORATE WITH CERTIFIED PROFESSIONALS
Experts Exchange is a tech solutions provider where users receive personalized tech help from vetted certified professionals. These industry professionals also write and publish relevant articles on our site.
Ask questions about what you read
If you have a question about something within an article, you can receive help directly from the article author. Experts Exchange article authors are available to answer questions and further the discussion.
Learn from the best.