Failed to load OpenSSL DLLS

Hello.

I just updated today to FlashFXP version - 4.4.3 (build 2031) and now I cannot connect to my servers that use SSL.

Here is the error that I get:

FlashFXP 4.4.3 (build 2031)
Support Forums http://forum.flashfxp.com
Winsock 2.2
[R] Connecting to Localhost -> IP=x.x.x.x PORT=990
[R] Connected to Localhost
[R] Failed to load OpenSSL DLLS. ssleay32.dll or libeay32.dll
[R] Connection failed (Connection closed by client)

I'm connecting via - FTP using Implicit SSL (SSLv3)

This just worked yesterday when I had build 2029.

Please advise as I have reinstalled FFXP and it didn't help.

Also, where could I download build 2029 in the mean time?

Please let me know if you need any more information from me.

Thanks.

Hello.

Just a quick update. I obtained a copy of the 2029 build but could not install it until I restarted my computer. For some reason the libeay32.dll and ssleay32.dll files were stuck in use and I could not overwrite them with the installer.

After a restart the install went perfectly and I'm now back to a functioning version of FFXP.

I tested out the update a second time and am able to reproduce the same problem.

Thanks.

So far I have not been able to determine the cause of this issue nor have I been able to reproduce the it on any of my machines.

We have the openssl dlls available as a separate download if you would like to do some testing

OpenSSL 1.0.1e

OpenSSL 1.0.1f


I will continue to investigate this issue.

Hi Bigstar.

I updated again today to test and everything is OK now.

I am thinking that when I tried the updater/installer the other day that maybe something was stuck running with FFXP or those DLL's.

Looks like a restart was all that was needed, although I have never had to do that after an update through FFXP.

Thanks for the follow up.

~L

Very strange.

The installer checks to ensure that FlashFXP isn't running before performing the update, however perhaps for whatever reason the OpenSSL dlls were still loaded into memory (maybe loaded into memory by some other application that was launched from within the local browser in FlashFXP) and the installer failed to update because of this.

Not really sure whats going on.

This is quite an interesting situation.