How To Change The Web Console Port

Products

• Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

Changing the port used for accessing the Web Console

Environment

• App Control Console: All Supported Versions
• Microsoft IIS: All Supported Versions

Resolution

1. Log in to the application server as the Carbon Black Service Account.
2. Stop the App Control Server and App Control Reporter services.
3. Open IIS Manager and in the left-hand pane expand: Server > Sites > right click Parity Console Web > Edit Bindings.
4. Select Add... and use the following details:
   • Type: https
   • IP Address: All Unassigned
   • Port: Relevant Port (Example: 8888)
   • Host Name: Leave blank
   • SSL Certificate: Use the relevant Certificate currently in use on port 443
     • Warning: Do not remove or disable the 443 port binding in IIS - instead, use the Firewall to block incoming 443
5. Open Notepad as an Administrator and edit the file: C:\Windows\System32\Drivers\etc\hosts
6. Add the Server's FQDN to the hosts file, example:

   127.0.0.1 appcontrol.acmewidgets.com
   ::1 appcontrol.acmewidgets.com

7. Use an administrative command prompt to issue the following command:

   iisreset

8. Start the App Control Server and Reporter services.
9. Log in to the Console using the new port in the URL. Example: https://ServerAddress:8888
10. Verify all pages work as expected, and Agents in Assets > Computers are continuing to report in.
11. Work with the Network Team (or use Windows Firewall) to block incoming requests on Port 443.

Update the Default Resource Download Location (needed when using the default settings)

1. Log in to the Console and navigate to System Configuration > Advanced > Edit.
2. Change the Resource Download Location to match:

   https://**ServerIP**:8888/hostpkg/pkg.php?pkg=

Additional Information

• The Console will continue to rely on the bindings for Port 443. Do not remove or disable that Port in IIS - instead, use the Firewall to block incoming 443
• When replacing the Agent Communication Certificate, the new certificate will need to be bound both to Port 443 and the new custom port, e.g., 8888, in IIS.