- Security >
- Manage Ops Manager Ports
Manage Ops Manager Ports¶
On this page
Overview¶
Ops Manager uses the ports and health-check endpoints described in Firewall Configuration. The endpoints are disabled by default. You can change Ops Manager’s default port and enable the endpoints.
Procedures¶
Change the Default Port on Unix-based Systems¶
To change the ports on Unix-based operating systems, you must edit
the port settings in <install-directory>/conf/mms.conf
, update the
Ops Manager URL in Ops Manager Config settings,
and restart Ops Manager.
Open mms.conf
for editing.¶
Open the mms.conf
file with root access. mms.conf
is located in the
<install_dir>/conf/
directory.
Set the BASE_PORT
value to the port Ops Manager should use.¶
By default, Ops Manager uses port 8080
. Change the BASE_PORT
value
to the desired port number.
If you wish to change the port for Ops Manager connections over SSL,
update BASE_SSL_PORT
.
When changing the port, ensure that the chosen port is available for use.
Edit the Ops Manager URL to use the new port.¶
In Ops Manager, click the Admin link in the upper right corner of the page.
Click the General tab and then click Ops Manager Config.
Update the URL to Access Ops Manager field to use the new port specified by the
BASE_PORT
:For example:
Click Save.
Restart Ops Manager.¶
Depending on how you installed Ops Manager, the command to restart Ops Manager will vary.
Installation with DEB
or RPM
package.¶
If you installed using a DEB
or RPM
package, use the following command to restart Ops Manager:
Installation from .tar.gz
archive.¶
If you installed using a .tar.gz
archive, use the following
command to restart Ops Manager:
Ops Manager will restart. The Ops Manager interface should be accessible at the new URL and port combination.
Change the Default Port on a Windows System¶
To change the ports on Windows, you need to edit the Windows registry, update the Ops Manager URL in Ops Manager Config settings, and restart Ops Manager.
Login to the Windows Host running Ops Manager.¶
Open the Registry Editor.¶
- Click Run from the Start menu.
- Type
regedit
. - Click OK.
- If User Access Control asks Do you want to allow this app to make changes to your device?, click Yes.
Open the Windows registry to the Java Options for Ops Manager.¶
By default, Ops Manager uses port 8080
for HTTP traffic and
8443
for HTTPS traffic. Edit the following registry value to
change either port:
Add one line for each desired port to the Options
multi-line registry value.¶
When changing either port, ensure that the chosen port is available.
For HTTP traffic to Ops Manager¶
Add a new line with -Dbase-port=<portnumber>
:
For HTTPS traffic to Ops Manager¶
Add a new line with -Dbase-ssl-port=<portnumber>
:
When you are done editing the settings, click OK, and exit the Registry Editor.¶
Edit the Ops Manager URL to use the new port.¶
In Ops Manager Application, click the Admin link in the upper right corner of the page.
Click the General tab and then click Ops Manager Config.
Update the URL to Access Ops Manager field to use the new HTTP (or HTTPS) port specified in the Java Options registry value.
Example
Click Save.
Restart Ops Manager.¶
To restart the Ops Manager HTTP service:
- Click Run from the Start menu.
- Type Services.
- Click OK.
- Right-click MongoDB Ops Manager HTTP Service.
- Click Restart.
Ops Manager restarts. The Ops Manager Application should be accessible at the new URL and port combination.
Enable the Health Check Endpoint¶
Ops Manager provides an HTTP health-check endpoint on port 8090 that is disabled by default. Before you enable the endpoint, ensure that port 8090 is available for use.
To enable the endpoint:
Open mms.conf
for editing.¶
Open the mms.conf
file with root access. mms.conf
is located in the
<install_dir>/conf/
directory.
Uncomment DEBUG.PORT
.¶
To enable the endoint, remove the #
symbol so that the line
reads:
Important
This port is only accessible from localhost
(or
127.0.0.1
). The port number can be changed from 8090
to
another value.