- My View
The MidServer communicates securely on port 443 to the instance and requires no inbound connections. In some cases, it might be necessary to allow this communication through the firewall if the MID Server fails to register on the instance. To determine if the application or a network security restriction is to blame for connection failure, attempt to telnet to the instance on port 443 from the server that is hosting the MID Server application. If this connection fails, then the problem could be a web proxy (since 443 is a https connecton) or a Firewall rule preventing external TCP connections from that host. Contact network security personnel for the proxy information to add to the config.xml file, or request that the Firewall be configured to allow access using one of the following syntaxes:
Additionally, ensure the MID server can connect to install.service-now.com to download and install updates.
as the mid server is configured in your network and the QRadar is also in your network, so you can communicate on any port you wish, even 443 is ok
Please Hit ✅Correct, ⭐️Helpful, or ❣️Like depending on the impact of the response