You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a bug, not a question or a configuration issue.
This issue is not already reported on Github (I've searched it).
Bug description
I'm trying to bind multiple 21 port on differents local address, the service crash on start.
I've double checked that nothing else is using that port.
Also tested on a fresh windows VM in Azure
From what i understand the problem come from ftpserverlib which is not handling properly a configuration where same port is bind on different ip address
Please find full logs and config attached with public ip address changed
Bug description
I'm trying to bind multiple 21 port on differents local address, the service crash on start.
I've double checked that nothing else is using that port.
Also tested on a fresh windows VM in Azure
From what i understand the problem come from ftpserverlib which is not handling properly a configuration where same port is bind on different ip address
Please find full logs and config attached with public ip address changed
sftpgo.json
Steps to reproduce
Expected behavior
FTP server should bind each socket (ip + port) without conflict.
SFTPGo version
2.6.2-636a1c2c-2024-06-21T17:20:51Z
Data provider
sqlite
Installation method
Other
Configuration
No env vars
sftpgo.json
Relevant log output
sftpgo.log
What are you using SFTPGo for?
Enterprise
Additional info
I've been trying to go around the bug by creating 4 different sftpgo instances, but did'nt succeed to create different SFTPGo services under windows.
I might be able to make a pull request for the fix with information on where the problem happen, in SFTPGo or ftpserverlib
Also i'd be able to provide you an Azure VM to test if it helps
thank you very much.
The text was updated successfully, but these errors were encountered: