Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Serv-U - Knowledgebase Articles > Serv-U Gateway installation instructions for Linux

Serv-U Gateway installation instructions for Linux

Updated March 1st, 2017


These instructions walk you through the process of installing and configuring Serv-U Gateway on Linux.


Serv-U 12.x and later


General Installation Process

  1. Install the software - automatically install as a service.
  2. Add Gateway entries in Serv-U Management Console.
  3. Add Listener entries in Serv-U domains to use the Gateway.
  4. Test external connectivity from file transfer clients.



Before proceeding with your installation, please ensure all of the following items are in place.

  • Existing Serv-U Server and Connectivity
    You must have already installed Serv-U on a server that can make connections to Serv-U Gateway. These connections may be (and probably will) be through a firewall and can be restricted to a single TCP port (1180 by default), but you must have this connectivity in place before you can complete your installation.
  • At Least One Serv-U Domain
    You must have at least one domain configured on Serv-U, and that domain should have at least one configured and active listener and at least one configured user.
  • Current Version of Serv-U
    Serv-U must be at least version 12, and must be running the same major edition of software (e.g., "v12") as your Gateway.
  • Separate Machine for Serv-U Gateway
    You must have a second machine (may be a virtual machine) on which you can install Serv-U Gateway.

Installation process

Perform these steps on the Serv-U Gateway machine.

  1. Download the appropriate installation file for 32-bit or 64-bit.
    32-bit: Serv-U-Gateway-Linux-x86-Install.bin
    64-bit: Serv-U-Gateway-Linux-x86_64-Install.bin
  2. Run chmod 777 (filename) on your installation file.
  3. Run either of the following and click through the prompts:
    sudo ./Serv-U-Gateway-Linux-x86-Install.bin
    sudo ./Serv-U-Gateway-Linux-x86_64-Install.bin

    If you are running from the command line and want to go a command-line installation, add a --mode console argument to your command to get prompted at the console. Or, add --mode silent to perform an unattended installation.
  4. Run ps -Al | grep Serv to verify that the "Serv-U-Gateway" process is running.
  5. Run sudo netstat -an -p | grep 1180 to verify that it is running on port 1180.

Add Gateway entries

Almost all Serv-U Gateway configuration is performed through the Serv-U Management Console. Serv-U Gateway does not have its own management console.

  1. Open the Serv-U Management Console and navigate to Server Details | Gateway.


Only perform these steps if you are testing Serv-U Gateway on a machine without a public IP address.

  1. Click Add to create a new Gateway entry.
    Gateway Address: the IP address of your Serv-U Gateway machine. 
    (If this machine has multiple addresses, pick the internal address that Serv-U will use to connect to the Gateway, not an external address that end users would access from the Internet. e.g., use "", not "")
  2. Port: 1180 
    (Leave alone for now.)
    Public IP Address: 
    (You may narrow this to only one binding later, but leave blank for now.)
    Enable Gateway: CHECKED 
    (You may toggle this setting later, but leave this on for now.)
    (Leave blank or put anything you want in here.)
  3. After you click Save, the new Gateway should immediately show up in the list. Pay attention to the color of the icon.
      KB2075_GIcon_green.png Great! Go to the next step.
      KB2075_GIcon_orange.png Serv-U is checking on the Gateway's status. Another status will appear in a few seconds.
      KB2075_GIcon_red.png The Gateway is working but you are running dangerously close to the end of your trial or updates/support period. You should plan to buy or renew soon, but you may also move on to the next step for now.
      KB2075_GIcon_red.png Something is wrong. Select the Gateway entry and then select "Properties" to find out why you cannot connect to your new Gateway.
    If you "fix" something (e.g., open a firewall port, start a stopped Serv-U Gateway service) it will normally take a few seconds for Serv-U to realize that a change has been made. To speed up the process, select your Gateway entry, "Edit" it and immediately "Save" your Gateway settings again.
  4. Apply a license, if you have it.
    To do this:
    1. Select the Gateway entry
    2. Select "Properties" to open the "Properties" dialog.
    3. Copy your Serv-U Gateway Registration ID (not a Serv-U Registration ID) into the box and click Save.
  5. If you are testing on a private network, declare one of your Gateway's internal IP addresses as the IP address that will receive incoming connections.
  6. To force your Serv-U Gateway to listen on a private address:
  7. Select your Gateway and click "Edit"
  8. Type the private address that will receive incoming connections into the "Public IP Address" box.
  9. Save and make sure the address you just typed shows up in your Gateway list.

Add Listeners entries

You must add Listener entries to each domain that will use your new Gateway.

  1. Go into one of your Serv-U domains and open Domain Details | Listeners.


  1. Before you add any Gateway Listeners, use an FTP client or web browser to sign on to one of your existing Listeners.
    The reason you want to do this now is to make sure that the user you will use to test your Gateway has been enabled, has access to the right materials, hasn't been locked out, etc. Make sure you test against one of the IP addresses on your existing Serv-U server, not the Serv-U Gateway.
  2. Click Add to create a new Listener entry.
    Type: Select the same type as the local Listener you just tested. 
    (Again, this ensures that server configuration is not the issue if you encounter problems during testing.)
    IP address: Select an IP address on your Serv-U Gateway. Use an external or "Internet-facing" address if possible. 
    (Use an internal address on the Serv-U Gateway only if you cannot test from "outside the firewall".)
    Port: Use the same port as the Listener you just tested. 
    (Exceptions: Use a port other than "22" if you are testing SFTP on a Gateway deployed on Linux. Also use a different port if you are testing Gateway on the same machine as Serv-U.)
    Enable listener: CHECKED
    PASV IP Address (FTP/S only): Leave blank for now. 
    (You may need to adjust this later, but work on basic connectivity first.)
  3. After you click Save, the new Listener should immediately show up in the list. Pay attention to the icon.
    KB2075_GIcon_ListenGood.png Great! Go to the next step.
    KB2075_GIcon_ListenGood.png There is a problem with the Listener. This could be due to a port conflict, due to a loss of connectivity with the Gateway or several other reasons. Check your Domain Log, then your System Log for more information.
  4. Check "Server Activity | Server Log" to make sure the Gateway has gone live.
    Look for entries like this: 
        GATEWAY on port 1180 is running as a TRIAL normally. IP(s): 
        GATEWAY ERROR: GATEWAY on port 1180 was NOT FOUND.
    These are both BAD entries. The first entry shows a connected Gateway, but this Gateway will not be able to listen for any inbound connections because the "IP(s)" entry is blank. The second entry shows a configured Gateway that cannot be reached. If you see either of these entries, STOP and check the work you did in the "Add Gateway Entry" section.
    Look for entries like this: 
        GATEWAY on port 1180 is running as a TRIAL normally. IP(s): 
        SFTP (SSH) server listening on GATEWAY ( port 1180) port number 2225, IP
    These are both GOOD entries. The first entry shows a connected Gateway that is ready to receive inbound connections on a particular IP address. The second entry shows that a SFTP Listener configured to listen on port 2225 is now ready to receive inbound connections. If you see entries like this, your Gateway and its Listeners are fine. Please proceed to the next section.


Test external Connectivity

Before you deploy to production (or perform a demonstration for management) you should perform an end-to-end connectivity test.

  1. Test your first Gateway Listener.
    Use the same client and same username you used to test your local Listener. Connect to the "Public IP Address" of your Gateway using the appropriate protocol and port for your first Gateway Listener.
  2. Flip back to the Serv-U Management Console and open "Domain Activity | Domain Log" to examine your connection.
    Look for entries like this: 
        SFTP (SSH) server listening on GATEWAY ( port 1180) port number 2225, IP 
        (000001) Connected to (local address, port 2225) 
        (000001) IP-Name: (
    These are all GOOD entries. The first entry shows that an inbound connection came in to an SFTP Listener on the Gateway. The second and third show that my Serv-U server (on has bound a session to the incoming session from the Gateway.
  3. If all is well, go to the next step. Otherwise, double-check you are really connecting to Serv-U Gateway or use the troubleshooting section below.
  4. Set up and test the rest of your Gateway Listeners by repeating the steps above.
    Also repeat these steps if you want to add additional IP addresses to your Gateway. (Gateway Listeners cannot currently bind to multiple IP addresses.)

Software update

Every update arrives as a complete installation package. Simply run a newer installation package to update your Serv-U Gateway software.

No backup is necessary on your Serv-U Gateway machine because no configuration is held there.

Unattended updates

To perform an unattended ("silent") update, use the "-silent" parameter when you invoke the installation program from the command line. Remember to run updates as root or use the "sudo" command to start the installation program. (Use of "sudo" is preferred.)


Follow this procedure to find the source of a connection error reported in Serv-U's Gateway tab.

  1. Check that the Serv-U-Gateway process is running.
  2. Check that Serv-U Gateway is listening on TCP port 1180 and is bound to the expected IP address(es).
  3. Check that network firewalls and routers permit TCP access over port 1180 from Serv-U to Serv-U Gateway.
  4. Check that local firewalls permit TCP access over port 1180 from Serv-U to Serv-U Gateway.

If you do not see your Serv-U Gateway IP address listed in a new Listener's IP Address drop-down.

  1. Ensure Serv-U is connecting to Serv-U Gateway OK. (E.g., a green icon in the Gateway list.)
  2. Make sure EITHER:
    • Your Serv-U Gateway machine has at least one public IP address
    • You performed step 5 in the Add Gateway Entries section above (because the Serv-U Gateway machine only has private IP addresses)

Helpful Commands

The process name is Serv-U-Gateway. Try:

  • ps -Al | grep Serv
  • sudo /etc/init.d/Serv-U-Gateway stop
  • sudo /etc/init.d/Serv-U-Gateway start
  • service Serv-U-Gateway start
  • service Serv-U-Gateway stop
  • service Serv-U-Gateway status
  • service Serv-U-Gateway restart


The default port Serv-U Gateway listens on is TCP 1180. Try:

  • netstat -an -p | grep 1180
  • sudo netstat -an -p | grep 1180


A common local Linux firewall is ipchains. Try:

  • sudo /etc/init.d/iptables status see if it is present and running.
  • sudo /etc/init.d/iptables stop temporarily shut it down to see if it is interfering.


The Gateway writes a limited bootstrap log here:

  • /usr/local/Serv-U Gateway/Serv-U-Gateway.txt


Additional assistance

See Planning Your Serv-U Gateway Deployment for a project template that allows you to select the right Serv-U architecture and coordinate with related IT teams to deploy Serv-U Gateway into production.

Additional assistance is available from our Technical Support Team.


Last modified