Weird behavior

[MattDelac]

Hello,

Here is my problem and I can't fix it:

Steps to reproduce:

• Launch atmoz/sftp with a docker-compose file (ports mapping / volume mounting / etc)
• Try to connect from a remote server with ssh keys => it works
• Launch a program that automatically copy files from a remote server (with an sftp command) => it works only the first time then starting the second time, it fails
• If a restart the docker, same behavior (it works only for the first time)

Remarks:

• I do not know where does it come from
• If I run the same program on a server where I use default sftp, there is no issue

I find iptables behavior strange as the host's port is 2342 but it writes a rule for port 22 (have a look to the following two picture)

Questions:

• Is there any timeout in atmoz/sftp ?
• Can it come from host's iptables or fail2ban ?
• Do you have any idea ?

Any help is warm welcomed

Thank you
Matt

[atmoz]

Can you share your docker-compose.yml?

Questions that pop up:

• Are you mounting your own ssh host keys?
• What does the output look like the second time you connect (sftp -v ...)?

[MattDelac]

Here it is

[atmoz]

So you do not have your own ssh host keys, but that will only be a problem when you re-create the container (new host keys are generated).

What did the debug output tell you (add the verbose flag as shown previously)?

[christianbur]

I just had the same problem.
I had to change the internal port for sftp, then I could connect from remote only. Before iptables always blocked port 22 even though it was mapped to 2222.

#382