Failed to Bind

View some of the Frequently Asked Questions to our support staff. Included are some tips and tricks making this forum ideal for users getting started with GoAnywhere MFT. Note: Users can reply to existing topics but only our support staff can add new topics to this forum.
1 post Page 1 of 1


User avatar
Support Specialist
Posts: 91
Joined: Thu Mar 05, 2009 3:49 pm
Location: Ashland, NE USA

Post by Support_Julie » Wed Feb 13, 2019 6:24 pm

When trying to start GoAnywhere MFT or the Gateway Manager within MFT, we see a “Failed to Bind” error.
2019-02-13 01:10:43 PM ERROR Failed to bind proxy on / com.linoma.gag.server.StartProxyFailedException: Failed to bind to: /01.01.01:22


The “Failed to Bind” error in the above example means that GoAnywhere attempted to connect to a port that is either:

1. Already in use by another application (in this case port 22)

2. Privileged, and the user account attempting to bind to this port is unable to do so.

Some takeaways:

1. Netstat is a common utility available in most versions of Windows, Linux, UNIX and other operating systems. Netstat provides information and statistics about protocols in use and current TCP/IP network connections. By using the Netstat command, you can determine what other application has the required port in use.

2. Many Linux/Unix systems require a root user in order to bind to ports under 1024. If you are running MFT with a non-root user account, you will need to choose ports above 1024. Our elegant solution to using standard ports is to use GoAnywhere Gateway and start Gateway with a root user profile. This allows you to map standard protocol ports on the Gateway server, and run MFT on ports like 8022 for SFTP. Due to the secure nature of Gateway, ownership of files is still handled by the non-root user account that starts MFT.
Julie Rosenbaum
Sr Support Analyst
e. [email protected]
p. 1.800.949.4696
1 post Page 1 of 1