IT Console Purchase GoMyid Remote Desktop

DeskGate troubleshooting and administration

Server Port Already in Use

Resolve a web or GateServer port conflict without stopping unrelated applications.

Maintained by DeskGate · Updated October 6, 2026

  1. 1. Identify the port

    Read the port number and component in the setup error.

  2. 2. Separate listeners

    Keep the web port outside the selected GateServer list.

  3. 3. Retry the preflight

    Verify local and intended network access.

Identify the conflict

The customer setup checks the selected ports before installation. A web port can be occupied by another listener or overlap with the selected GateServer list. Record which port and component the inline error identifies.

The web interface default is 5000. GateServer uses its selected default-port list; these are separate listeners. Opening a firewall rule cannot resolve a port already occupied by another application.

Review the actual setup controls

Web interface port and Customize GateServer ports in server setup
Actual installer in non-installing preview mode; example values and success messages are illustrative. Open the image for its original size.
  1. Review Web interface port and the selected GateServer ports.
  2. If the web port is occupied, choose another available web port approved for the deployment. For example, port 5020 would use http://localhost:5020/ on the server.
  3. Use Customize GateServer ports only to remove default ports that your deployment does not need. Keep at least one. The Release wizard does not accept additional or duplicate GateServer ports.
  4. If another application owns a required port, ask its administrator to identify its purpose before making a change. Do not stop it blindly.
  5. Retry Install and confirm that the port preflight no longer reports the conflict.

Do not confuse binding with network access

With Allow network access off, the web interface is local to the server. With it on, GateCore listens on all IPv4 interfaces and setup adds an inbound TCP rule for the selected web port. Use the server’s assigned address and chosen port for the authorized network check. GateCore access policy still applies.

If localhost works but another computer cannot connect, investigate access mode, destination address, routing and the scoped firewall rule. That is a different symptom from an occupied port. Network mode does not automatically configure HTTPS or a public hostname.

Confirm and document

Complete the setup checks and open the web interface on the new port. Verify from another authorized computer only when network access is intended. Update administrator bookmarks and the deployment record with the accepted port.

If the conflict remains, record the release, requested web/GateServer ports and exact error for support. Follow the illustrated server setup guide for the complete sequence.