<

[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x

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

Published on
3,665 Points
565 Views
1 Endorsement
Last Modified:
Luciano Patrão
My main areas of expertise are VMware, Virtual Backups and Storage design.
I am a vExpert and a Technical Blogger in the same areas.
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
Comment
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
0 Comments

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Join & Write a Comment

Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month