Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Changing the port used by the vSphere Client to connect directly to the ESX/ESXi host (1021199)

Last Updated: 4/17/2017Categories: How toTotal Views: 131964Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Details

By default, the vSphere Client uses HTTP port 80 and HTTPS port 443 to communicate with ESX/ESXi hosts. You can change these ports with these methods:

Change the ports configured in proxy.xml on the host.

Change the ports configured for the vSphere Client.

Solution

To change the ports configured in proxy.xml:

ESX

Log in to the service console and acquire root privileges.

Change to the /etc/vmware/hostd/ directory.

Edit the proxy.xml file with a text editor, and add these tags under the <ConfigRoot> tag:

<httpPort>xx</httpPort>
<httpsPort>xxx</httpsPort>

where xx is the port you want to use for HTTP traffic and xxx is the port you want to use for HTTPS traffic.

Example: To configure port 8080 as the port for the HTTP connection, and port 8081 as the port for the HTTPS connection, add these two lines:

<httpPort>8080</httpPort>
<httpsPort>8081</httpsPort>

Enter this command to restart the vmware-hostd process:

service mgmt-vmware restart

ESXi

Run the vifs command to get a copy of the proxy.xml file to edit:

For Linux systems, use this command:

vifs --server <hostname<em>> --username <username<em>> --get /host/proxy.xml <local_directory_path<em>>/proxy.xml

For Windows systems, use this command:

vifs --server <hostname<em>> --username <username<em>> --get /host/proxy.xml <local_directory_path<em>>\proxy.xml

Edit the proxy.xml file with a text editor, and add these tags under the <ConfigRoot> tag:

<httpPort>xx</httpPort>
<httpsPort>xxx</httpsPort>

where xx is the port you want to use for HTTP traffic and xxx is the port you want to use for HTTPS traffic.

Example: To configure port 8080 as the port for the http connection, and port 8081 as the port for the https connection, add these two lines:

<httpPort>8080</httpPort>
<httpsPort>8081</httpsPort>

Run the vifs command to place the proxy.xml file back on the ESXi host:

For Linux systems, use this command:

vifs --server <hostname> --username <username> --put <local_directory_path>/proxy.xml /host/proxy.xml

For Windows systems, use this command:

vifs --server <hostname> --username <username> --put <local_directory_path>\proxy.xml /host/proxy.xml

Notes:

The vifs command requires the remote CLI application to be installed on the Workstation where the CLI is installed. You can download the vSphere Management Assistant (vMA) from theVMware download center .

For vSphere 5.0, if the proxy ports are changed, the new ports are not allowed through the ESXi firewall. For information on how to change the firewall ports, see the vSphere Security Guide.

Making changes to the ESXi 5.0 firewall currently do not persist after a reboot.

Use the Restart Management Agents operation through the direct console to restart hostd.

To change the ports configured for the vSphere Client in the client configuration file:

On the system where the vSphere Client is installed, edit the VpxClient.exe.config client configuration file with a text editor. By default, this file is located at C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\

Edit this line in the file to change the HTTP and HTTPS ports:

<add key = "protocolports" value = "https:443;http:80:" />

Example: Tto change the HTTP port to 8080 and the HTTPS port to 8081, change the line to:

<add key = "protocolports" value = "https:8081;http:8080" />

As an alternative to editing the vSphere Client configuration file, you can specify the HTTPS port on the login screen of the vSphere Client by entering <servername>:<https_port_number> in the IP address / Name text box.

Note: For more information about TCP/UDP ports, see TCP and UDP Ports required to access vCenter Server, ESX hosts, and other network components (1012382).

Additional Information

For translated versions of this article, see:

Español: Cambiar el puerto utilizado por el vSphere Client para conectarse directamente al host ESX/ESXi (2035793)

Português: Como alterar a porta usada pelo vSphere Client para se conectar diretamente com o host ESX/ESXi (2037239)

日本語: vSphere Client が使用するポートを変更し、ESX/ESXi ホストへ直接接続する (2078747)

简体中文: 更改 vSphere Client 用来直接连接到 ESX/ESXi 主机的端口 (2075132)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESX 4.1.x

VMware ESX 4.0.x

Take Our Survey

Support Assistant