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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Changing or blocking the default ports 80 (http) and 443 (https) on ESX hosts (1007289)

Last Updated: 3/20/2024Categories: Total Views: 42807Language:
English

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Purpose

This article provides steps to change or the block the default ports 80 (http) and 443 (https) that vmware-hostd listens on.

Resolution

Changing the default ports

ESX 3.0.x

To change the default ports 80 (http) and 443 (https) for ESX 3.0.x:

Open the /etc/vmware/hostd/config.xml file with a text editor.

Locate the following XML segment:

<proxysvc>
<path>/usr/lib/vmware/hostd/libproxysvc.so</path>
<http>
<port>80</port>
<proxyDatabase>
<server id="0">
<namespace> / </namespace>
<host> localhost </host>
<port> 9080 </port>
</server>
<redirect id="0"> /ui </redirect>
<redirect id="1"> /mob </redirect>
<redirect id="2"> /sdk </redirect>
</proxyDatabase>
</http>
<https>
<port>443</port>
<proxyDatabase>
<server id="0">
<namespace> / </namespace>
<host> localhost </host>
<port> 9080 </port>
</server>
<server id="1">
<namespace> /sdk </namespace>
<host> localhost </host>
<port> 8085 </port>
</server>
<server id="2">
<namespace> /ui </namespace>
<host> localhost </host>
<port> 8080 </port>
</server>
<server id="3">
<namespace>/mob</namespace>
<host>localhost</host>
<port>8087</port>
</server>
</proxyDatabase>
/https>
</proxysvc>

Change the http and https port numbers and save the file.

Restart the vmware-hostd process with the command:

# service mgmt-vmware restart

ESX 3.5.x / ESX 4.0

To change the default ports 80 (http) and 443 (https) on ESX 3.5.x or ESX 4.0:

Open the /etc/vmware/hostd/proxy.xml file with a text editor.

Under <ConfigRoot>, add the following entry:

<httpPort>custom port #</httpPort>

<httpsPort>custom port #</httpsPort>

For example:

<httpPort>81</httpPort>

<httpsPort>444</httpsPort>

Save the file.

Restart the vmware-hostd process with the command:

# service mgmt-vmware restart

ESX 4.0

You can open service console firewall ports when you install third-party devices, services, and agents. Before you open ports to support the item you are installing, see vendor specifications to determine the necessary ports.

To open ports for services or agents that are not configurable through the vSphere Client:

Caution: VMware supports opening and closing firewall ports only through the vSphere Client or the esxcfg-firewall command. Using any other methods or scripts to open and close firewall ports can lead to unexpected behavior.

Log in to the service console and acquire root privileges.

Use the following command to open the port:

esxcfg-firewall --openPort <port_number>,tcp|udp,in|out,<port_name>

Where:

<port_number> is the vendor-specified port number.

Use tcp for TCP traffic or udp for UDP traffic.

Use in to open the port for inbound traffic or out to open it for outbound traffic.

<port_name> is a descriptive name to help identify the service or agent using the port. A unique name is not required.

For example:

esxcfg-firewall --openPort 6380,tcp,in,Navisphere

Run the following command to restart:

# service mgmt-vmware restart

Note: VMware does not support configuring a different port for port 443. For more information, see Connecting to the Virtual Machine Console Through a Firewall in the ESX Configuration Guide.

Blocking the default ports

Note: The information in this section pertains to ESX 3.x and ESX 4.0.

You cannot block port 80 and 443 using the esxcfg-firewall commands. These commands return an error indicating that the port is not open.

Custom ports are blocked by default. To open a custom port, issue the following command:

esxcfg-firewall -o <port,tcp|udp,in|out,name>

For example:

esxcfg-firewall -o 81,tcp,in,http

Related Information

The following ports are opened by default:

22

80

443

902

5988

5989

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
vCenter Server サービスが、データベース接続を失った場合に、シャットダウンしない (2007542)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESX Server

Related Versions:

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant