Migrating License of MFT 5.5.5 On Automated Build

If you have a new question you’d like our support staff to post a response to, please visit our customer community, Data Security Insiders, to pose the question in our Discussion Boards. We have a thread “Ask Our Tech Experts” that our support team monitors on a regular basis, or you can start a new discussion where other GoAnywhere users and support staff can weigh in. Log in or create your new account at https://insiders.helpsystems.com/sign_in.

If you need an immediate response, please create a support ticket or contact our support team by email at [email protected].
2 posts Page 1 of 1


Posts: 4
Joined: Thu Dec 01, 2016 10:34 am

Post by dbeckman » Wed Jul 12, 2017 10:12 am
We've been testing an automated build of GA MFT 5.5.5. running on RHEL 7.3. We use Puppet to lay down the GA binaries and configuration files. We tested this on a staging server and tried deploying to a new production server (which will replace the staging server) and ran into an issue related to licensing. We had moved the existing license file, shut down the old server, and had given the new server the same MAC address. But when the new server starts up, we get this in the logs and it exits:

7/11/17 3:43:05 PM ERROR Error refreshing license
java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:625)
at com.linoma.dpa.util.TrustingSSLProtocolSocketFactory.createSocket(Unknown Source)
at org.apache.commons.httpclient.HttpConnection.open(Unknown Source)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Unknown Source)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(Unknown Source)
at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source)
at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source)
at com.linoma.ga.core.license.ProductLicenseController.refreshLicense(Unknown Source)
at com.linoma.ga.core.license.ProductLicenseAPI.refreshLicense(Unknown Source)
at com.linoma.startup.TomcatStarter.start(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.linoma.bootstrap.GoAnywhereBootstrap.main(GoAnywhereBootstrap.java:95)


I did look at this article:

However, we were hoping for a more automated approach. We'd like to setup a GA MFT deployment that could be re-provisioned at any time, even by someone not familiar with the product.

Is MFT trying to "phone home" to Linoma to check or refresh the license? Does it do that at each startup or only when changes are detected? What host does it contact and on what port? Our default firewall rules are restrictive and prevent most outbound traffic. If this is a connectivity issue we'll need to know exactly what it uses.

Any help would be appreciated!

Daniel Beckman
Ingram Content Group


Posts: 34
Joined: Mon Dec 01, 2014 10:35 am

Post by Support_Tim » Fri Jul 14, 2017 10:28 am
Hi DBeckman,
When GoAnywhere is started, it tries to connect to our license server to look for changes to the license, just as it would if you click "Refresh" from the license screen. If it is unable to reach the license server, it shows this error in the log. This is not uncommon and does not indicate any other problem with GoAnywhere.

If you would like to eliminate this error and allow the GA license to refresh, you need to make sure that your firewall rules allow outbound HTTP/s access from the GA server to my.goanywhere.com. We use the standard ports, 80 and 443.
2 posts Page 1 of 1