Tools

Troubleshoot and Resolve Serv-U Gateway Connectivity Issues Caused by IP Address Changes

This article provides step-by-step guidance to troubleshoot Serv-U Gateway connectivity problems, particularly those caused by IP address changes. It helps identify configuration mismatches and ensures proper communication between Serv-U and the Gateway.

First published date

10/18/2018 2:11 AM

Last published date

7/29/2025 10:25 PM

Overview

This article provides step-by-step troubleshooting guidance for resolving common issues with the Serv-U Gateway with error messages:

 

HTTP server listening on port number 43958, IP 127.0.0.1
HTTP SERVER IS NOT LISTENING ON IP ::1: Trying to use non-existent IP address?

HTTP SERVER IS NOT LISTENING ON IP  XX.XX.XXX.X:: Trying to use non-existent IP address?
SFTP (SSH) SERVER IS NOT LISTENING ON IP XX.XX.XXX.X: Trying to use non-existent IP address?

Product section

Serv-U Managed File Transfer & Serv-U FTP Server

Cause

These issues occur because the Serv-U Gateway service is not running properly, is not listening on the correct IP address or port, or when network/firewall configurations block communication.

Resolution

Verify Gateway Logs

The Serv-U Gateway writes a limited bootstrap log to help diagnose issues

    C:\ProgramData\RhinoSoft\Serv-U Gateway\Serv-U-Gateway.txt

Review this log for any error messages or warnings.

Perform Basic Connectivity Checks

  • Confirm the Serv-U Gateway Windows Service is running.
  • Verify that the Gateway is listening on TCP port 1180 and bound to the expected IP address(es).
  • Ensure that network firewalls and routers allow TCP traffic on port 1180 between Serv-U and Serv-U Gateway.
  • Check local firewall settings on both Serv-U and Gateway machines to permit TCP access on port 1180.

Confirm Gateway IP Address Visibility

If your Serv-U Gateway IP address does not appear in the Listener’s IP Address drop-down when configuring a new Listener:
  • Verify Serv-U is successfully connected to the Serv-U Gateway (look for a green icon in the Gateway list).
  • Ensure the Serv-U Gateway machine has at least one public IP address assigned.


Change the Gateway IP Address entry in the Management Console

  1. Go to the Serv-U Management Console
  2. Go to Global > Server Details > Serv-U Gateway tab
  3. If the Gateway Address is different from the Public IP Address, use the Gateway Address as the Public IP Address as well

Before:

 

After:

  1. Update all Domain Listeners to use the new Gateway IP address.

Additional Notes

  • After making changes, restart the Serv-U Gateway service if necessary to apply updates.
  • Ensure all network devices between Serv-U and the Gateway allow required traffic.