Start a new topic

CrushFTPDrive Not Working Anymore

None of our users are able to log in with CrusFTPDrive anymore.  I have verified that I can log into the web portal through a browser from an affected client machine, however, when we launch the CrushFTPDrive.jnlp file, it takes a while to download the application, and seems to time out.  Then Java says that it is unable to launch the application and has the following exception.  Again, I can access the web portal on the same port.  I have even tried restarting the CrushFTPServer Windows service, as well as the client machines.  I have also tried disabling the client machine's firewall and AntiVirus.

Error Information:
java.net.SocketException: Software caused connection abort: socket write error

 at java.net.SocketOutputStream.socketWrite0(Native Method)

 at java.net.SocketOutputStream.socketWrite(Unknown Source)

 at java.net.SocketOutputStream.write(Unknown Source)

 at sun.security.ssl.OutputRecord.writeBuffer(Unknown Source)

 at sun.security.ssl.OutputRecord.write(Unknown Source)

 at sun.security.ssl.SSLSocketImpl.writeRecordInternal(Unknown Source)

 at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)

 at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)

 at sun.security.ssl.Handshaker.sendChangeCipherSpec(Unknown Source)

 at sun.security.ssl.ClientHandshaker.sendChangeCipherAndFinish(Unknown Source)

 at sun.security.ssl.ClientHandshaker.serverHelloDone(Unknown Source)

 at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)

 at sun.security.ssl.Handshaker.processLoop(Unknown Source)

 at sun.security.ssl.Handshaker.process_record(Unknown Source)

 at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)

 at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)

 at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)

 at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)

 at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)

 at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)

 at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)

 at sun.net.www.protocol.http.HttpURLConnection.access$200(Unknown Source)

 at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)

 at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)

 at java.security.AccessController.doPrivileged(Native Method)

 at java.security.AccessController.doPrivilegedWithCombiner(Unknown Source)

 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)

 at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)

 at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source)

 at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)

 at com.sun.deploy.net.BasicHttpRequest.doGetRequestEX(Unknown Source)

 at com.sun.deploy.cache.ResourceProviderImpl.checkUpdateAvailable(Unknown Source)

 at com.sun.deploy.cache.ResourceProviderImpl.isUpdateAvailable(Unknown Source)

 at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)

 at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)

 at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source)

 at java.util.concurrent.FutureTask.run(Unknown Source)

 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

 at java.lang.Thread.run(Unknown Source)



This is not a connectivity issue to the CrushFTP server...but rather connectivity between Java and the SSL certificate that the jar is signed with.  Java is trying to validate that the cert is good...and can't reach the cert authorities servers due to firewall blocking...


Its signed with a go daddy cert, so its one of their servers being blocked...

Is it being blocked on the client or on the CrushFTP server?  They are 2 different networks behind separate corporate firewalls, but are connected through a site-to-site VPN with split-tunneling allowed, so I would need to look at the appropriate network settings.

The client machine can't reach the very authority to validate the code is valid. Nothing to do with CrushFTP at all.
Login to post a comment