SSH Bash CLI into Filezilla Server on Windows

Need help with FileZilla Server? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
himuken
500 Command not understood
Posts: 1
Joined: 2024-02-20 19:35
First name: Darius
Last name: Diep

SSH Bash CLI into Filezilla Server on Windows

#1 Post by himuken » 2024-02-20 19:39

Hi, I am trying to Putty into the Shell cmd for filezilla to disable the SSH key
Anyone able to direct? Getting ""Server refused to Start a shell/command"
Here are the server log:
2024-02-20T07:01:49.260Z == Setting up SSH
2024-02-20T07:01:49.260Z == [SSH SFTP Server] Using SSH host key (ssh-ed25519) with fingerprint: SHA256:+cXmcXz8G7cKbwYuBr1leyTDdg+ERbzBeruMImJzs/g
2024-02-20T07:01:49.260Z == [Administration Server] The license is valid.
2024-02-20T07:01:49.260Z == [FTP Server] Listening on 0.0.0.0:21.
2024-02-20T07:01:49.260Z == [FTP Server] Listening on [::]:21.
2024-02-20T07:01:49.260Z == [SSH SFTP Server] Listening on 0.0.0.0:22.
2024-02-20T07:01:49.260Z == [SSH SFTP Server] Listening on [::]:22.
2024-02-20T07:01:49.260Z == [Administration Server] Listening on 127.0.0.1:14148.
2024-02-20T07:01:49.260Z == [Administration Server] Listening on [::1]:14148.
2024-02-20T09:02:40.130Z == [SSH SFTP Session 1 10.0.0.32] Closing connection

Code: Select all

2024-02-20T09:02:40.130Z == [SSH SFTP Server] Session 1 ended gracefully.
2024-02-20T13:02:45.072Z == [SSH SFTP Session 2 10.0.0.32] Closing connection [code=106]
2024-02-20T13:02:45.072Z !! [SSH SFTP Server] Session 2 ended with error. Reason: ECONNABORTED - Connection aborted.
2024-02-20T17:02:42.988Z == [SSH SFTP Session 3 10.0.0.32] Closing connection [code=106]
2024-02-20T17:02:42.988Z !! [SSH SFTP Server] Session 3 ended with error. Reason: ECONNABORTED - Connection aborted.
2024-02-20T19:29:01.271Z == [Administration Server] Administration client with ID 4 connected from 127.0.0.1:52444

[i]
I found the solution. It is very simple.
Just start filezilla from a bash setting SSH_AUTH_SOCK to something other than the ssh agent (null or whatever you might fancy):
CODE: SELECT ALL

machine@user:~$ SSH_AUTH_SOCK=null filezilla &
This sets the SSH_AUTH_SOCK shell environment variable only for this instance of filezilla, which means any other program (e.g. ssh) can still use the agent while filezilla wont be able to do so.
You can even start a second instance of filezilla that does use the ssh-agent for the servers you want to authenticate to with pubkey auth:
CODE: SELECT ALL

machine@user:~$ filezilla &
The & at the end simply starts the preceding command in the background so you can continue using the shell for starting more commands.

And yes, I had the idea of compiling my own filezilla and got stuck in dependency hell before thinking of simple bash logic.

May all poor souls that suffer from the filezilla behavior with ssh-agent find their way here!

Cheers, vin[/i]

User avatar
botg
Site Admin
Posts: 35566
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: SSH Bash CLI into Filezilla Server on Windows

#2 Post by botg » 2024-02-20 22:23

FileZilla Pro Enterprise Server support is located at https://customerforum.filezilla-project.org/

Post Reply