Server security update reboot: SFTPGo doesn't start

[imc67]

This morning I needed to perform a security update reboot and after that SFTPGo doesn't start.

Docker Error: (HTTP code 500) server error - driver failed programming external connectivity on endpoint 98d1b4c0-********-729c3077a061 (cec35e817f384c6cd2***1608926aff5ce2d176a64da69d4f): failed to bind port 0.0.0.0:41090/tcp: listen tcp4 0.0.0.0:41090: bind: address already in use

I tried to restart the task many many times (MiroTalk also has sometimes this issue), tried to restore a backup, etc. etc. .... it doesn't start.

Is there somehow a way to force this? My use of SFTPGo is critical as it is a central backup location for many "IOT appliances".

[james]

Hello @imc67
The issue why your SFTPGo is not starting is because 0.0.0.0:41090: bind: address already in use.
I highly suspect this is just temporary and if you stop the app for 2–5 minutes and then start the app again, this will resolve itself.

You can also run the following on your root:

lsof -i :41090 -S

to see if really anything is using that port.

[imc67]

@james said in Server security update reboot: SFTPGo doesn't start:

You can also run the following on your root:

lsof -i :41090 -S
to see if really anything is using that port.

yes:

~# lsof -i :41090 -S
COMMAND PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
ssh     940 root    3u  IPv6  25971      0t0  TCP [2a03:****:5f:dc5:48ba:****:fe45:61f0]:41090->[2a01:4f8:****:1635::2]:telnet (ESTABLISHED)

What could it be? I already stopped MiroTalk and Nextcloud

[imc67]

BTW: I also restarted Docker via the GUI but it also didn't solved it.

[imc67]

Thanks to ChatGPT I could solve it:

"Something" outside Docker was claiming this port

sudo kill 940

Killed this connection, now the restore worked and the app started.

[james]

This might have been a lingering connection from one of your IoT devices.

ssh     940 root    3u  IPv6  25971      0t0  TCP [2a03:REDACTED:61f0]:41090->[2a01:REDACTED::2]:telnet (ESTABLISHED)

The program used was ssh so I assume a lingering sftp connection since SFTP uses SSH as the binding agent.
If you can find out what or who 2a03:REDACTED:61f0 and 2a01:REDACTED::2 is you might find the device that had the connection still open.

[imc67]

Thanks for the hint, I investigated further:
The left IPv6 is my Cloudron server, from there is had an active connection (ssh outside of Docker) to the right IPv6 my storage box!

I only use 1 Volume to a Storagebox and 1 Backup location. Could it be that one of those 2 uses the same port-range (41000+100)? @girish

BTW: @James please redact my ip's in your message (I just corrected mine)

[imc67]

said in Server security update reboot: SFTPGo doesn't start:

Thanks for the hint, I investigated further:
The left IPv6 is my Cloudron server, from there is had an active connection (ssh outside of Docker) to the right IPv6 my storage box!

I only use 1 Volume to a Storagebox and 1 Backup location. Could it be that one of those 2 uses the same port-range (41000+100)? @girish

BTW: @James please redact my ip's in your message (I just corrected mine)

@girish is this a bug? There are more topics with the same kind of error message