Ports not to be used for HTTPS management - SonicWall UTM

08/13/2024 0 People found this article helpful 49,122 Views

Description

This KB throws light on a few ports that should not be used for the HTTP/s Management page. Creating a custom port for HTTP/s management is often recommended practice. Configuring a custom port for Management page is explained in the below KB article:

How to change the HTTP and HTTPS management ports on UTM Appliances?

Cause

There are a few ports used that are reserved for internal communication between SonicOS and SonicCore. When you use these ports for the Management page, it throws an error "Invalid port" or "Reserved for SonicOS use".

Resolution

The list of the ports are:
- - TCP port 1
  - TCP port 19
  - TCP port 20
  - TCP port 21
  - TCP port 25
  - TCP port 110
  - TCP port 119
  - TCP port 143
  - TCP port 220
  - TCP port 993
  - TCP port 65011
  - TCP port 65012
  - TCP port 65443
CAUTION: This restriction is only for Management port, and NOT for any port forwarding or other inbound access
SSL VPN | Server port mentioned in this KB: SSLVPN on a Different TCP Port should not be used.
Other ports used for external communication like licensing manager, signature downloads etc. are listed in the KB given below. They are for outbound traffic from the respective SonicWall interface IP and will not conflict with any other traffic from the firewalled/VPN subnets.