PLESK hiccup in Net FTP

English support forum

Moderators: white, Hacker, petermad, Stefan2

Post Reply
fuzmic
Junior Member
Junior Member
Posts: 25
Joined: 2015-09-14, 05:05 UTC

PLESK hiccup in Net FTP

Post by *fuzmic »

Admin

I use NET FTP to connect to Linux server with usual CPanel, perfect with your 2 TCom panel. Great!

However when i try the same to server with Plesk control panel it slow at MLSD and finally report it failed to resolve with title "PASV" saying port failed. I have been told in plesk the port for FTP is changed to 1373 but i don't know its significance or how to resolve this hiccup.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: PLESK hiccup in Net FTP

Post by *ghisler(Author) »

Port 1373 is just for login and sending commands to the FTP server. The actual files and directory lists are sent via separate data connections on separate ports. It sounds like the FTP data ports are not open in your firewall.

Here is some info for Plesk Obsidian to configure passive FTP ports:
https://docs.plesk.com/en-US/obsidian/administrator-guide/server-administration/plesk-for-linux-configuring-passive-ftp-mode.74643/
Author of Total Commander
https://www.ghisler.com
fuzmic
Junior Member
Junior Member
Posts: 25
Joined: 2015-09-14, 05:05 UTC

Re: PLESK hiccup in Net FTP

Post by *fuzmic »

Thank you Ghisler for the pepetual advice. Question whose FTP data port is not open, is it the server port since i can access other servers using your TC.
Another observation; the mobile version of your TC can access the unaccessible server.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: PLESK hiccup in Net FTP

Post by *ghisler(Author) »

Do you use passive mode in the plugin? If not, then disable passive mode in the Windows version too.

Otherwise your server may be set to use SSL session resumption, which isn't supported any more by the SSL library built into Windows. You will need to use the OpenSSL DLLs in this case:
https://www.ghisler.com/whatsnew.htm#ftps
Author of Total Commander
https://www.ghisler.com
fuzmic
Junior Member
Junior Member
Posts: 25
Joined: 2015-09-14, 05:05 UTC

Re: PLESK hiccup in Net FTP

Post by *fuzmic »

Thank you Bruder for the hint on passive mode. I seem to be getting some result by selecting "Select PASV by default" in the configuration > FTP but i would like to share what i encounter hoping you can pick up any new pointers.

My observation with this option
1 first response states port 200 command sent but failed then will try PASV
2 at PASV a net panel states the correction connection but it is blank
3 at blank panel i do a Ctri_R to reread, sometimes it will display the server folders immediately but something i need to reconnect then it wil show the folders from the server.

Bruder what is your take on this.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: PLESK hiccup in Net FTP

Post by *ghisler(Author) »

I seem to be getting some result by selecting "Select PASV by default" in the configuration > FTP
That's just for new connections. There is a separate passive mode option in each configured connection.
1 first response states port 200 command sent but failed then will try PASV
That means that active (PORT) mode) is being blocked, probably by a firewall.
So the issue here isn't passive mode, it's the session resumption problem I mentioned above. Try unpacking the openssl dlls to the TC directory as described on the linked page:
https://www.ghisler.com/whatsnew.htm#ftps
Author of Total Commander
https://www.ghisler.com
fuzmic
Junior Member
Junior Member
Posts: 25
Joined: 2015-09-14, 05:05 UTC

Re: PLESK hiccup in Net FTP

Post by *fuzmic »

Bro
So i notice that configuration > option > FTP on PASV has no effect as you have stated ie it does not matter if i set "use passive mode by default" the ctrl-R is requiired for the same positive effect.

I downloaded openssl.zip from the 64-bit link and placed in plugin sub-folder as the following DIR info shows

Directory of c:\Program Files\TCom\PLUGINS
21-12-19 07:01 PM 1,161 HashInfo.txt
21-12-19 07:01 PM 2,293,248 libeay32.dll
31-08-16 07:13 PM 6,404 OpenSSL License.txt
21-12-19 07:00 PM 548,352 openssl.exe
21-12-19 07:01 PM 2,722 ReadMe.txt
21-12-19 07:01 PM 386,560 ssleay32.dll

However there is no effect. Any thing to add. Thank you.
User avatar
white
Power Member
Power Member
Posts: 4595
Joined: 2003-11-19, 08:16 UTC
Location: Netherlands

Re: PLESK hiccup in Net FTP

Post by *white »

ghisler(Author) wrote: 2023-02-27, 09:45 UTC Try unpacking the openssl dlls to the TC directory as described on the linked page:
https://www.ghisler.com/whatsnew.htm#ftps
There is a link there pointing to https://www.ghisler.com/openssl/, which says:
www.ghisler.com/openssl/ wrote:Unzip the 32-bit dlls to the Total Commander or plugin directory. The 64-bit dlls go to the subdirectory named "64" (without the quotes).
I think this means that:
  • The dlls (other files are not needed) should be placed in the Total Commander program folder. 64-bit dlls should be placed in a subfolder called "64".
  • If you use a plugin you can alternative place the dlls in the folder where the plugin is installed. 64-bit dlls should be placed in a subfolder called "64".

fuzmic wrote: 2023-02-28, 07:18 UTC I downloaded openssl.zip from the 64-bit link and placed in plugin sub-folder as the following DIR info shows

Directory of c:\Program Files\TCom\PLUGINS
...
So, that's not the right place. The 64-bit dlls should be placed in: c:\Program Files\TCom\64



2ghisler(Author)
www.ghisler.com/openssl/ wrote: Download links: 32-bit | 64-bit

The page indy.fulgan.com, from which these DLLs come, is current not available.
The page page indy.fulgan.com is available now from my ip address, but the Indy projects website says:
www.indyproject.org/download/ssl/ wrote: SSL DLL Download

Because of export restrictions we do not provide the DLLs directly.
So, I suggest to change the link on your website to the GitHub repository.
Post Reply