I’m new to rockstor and fight the hole day to keep the sftp connection running but without luck…
To my setup:
Rockstor is running on an Intel Machine (nativly without VM) and fixed IP address
on my firewall appliance / router (OpnSense) I have configured two port forwardings from two custom ports on the WAN side to 443 for the GUI and 22 for SSH / SFTP
access was tested from remote side with windows machines using the clients WinSCP, MobaXterm and Cyberduck (all with the same result)
What is working:
Access of the Rockstor GUI
establishing a SSH session with putty, but unfortunately I haven’t the root passwort present (only from the second admin account on the GUI) therefore I can only verify until the password promt
What was done for user creation:
setting up a user with his one group
create a share within the pool created during instalation (rockstor_rockstor)
setting the user as owner of the share
add a sftp share to the obove created share and enable the SFTP Service
The result:
Win SCP connect to the server, checking the password and username garant access and than the server disconnects the connection.
Following an part from the ftp client log file:
. 2018-07-31 14:29:05.521 Opening session as main channel
. 2018-07-31 14:29:05.521 Waiting for the server to continue with the initialization
. 2018-07-31 14:29:05.521 Looking for incoming data
. 2018-07-31 14:29:05.521 Looking for network events
. 2018-07-31 14:29:05.540 Detected network event
. 2018-07-31 14:29:05.540 Enumerating network events for socket 1844
. 2018-07-31 14:29:05.540 Enumerated 1 network events making 1 cumulative events for socket 1844
. 2018-07-31 14:29:05.540 Handling network read event on socket 1844 with error 0
. 2018-07-31 14:29:05.540 Opened main channel
. 2018-07-31 14:29:05.541 Waiting for the server to continue with the initialization
. 2018-07-31 14:29:05.541 Looking for incoming data
. 2018-07-31 14:29:05.541 Looking for network events
. 2018-07-31 14:29:05.621 Detected network event
. 2018-07-31 14:29:05.621 Enumerating network events for socket 1844
. 2018-07-31 14:29:05.621 Enumerated 1 network events making 1 cumulative events for socket 1844
. 2018-07-31 14:29:05.621 Handling network read event on socket 1844 with error 0
. 2018-07-31 14:29:05.621 Started a shell/command
. 2018-07-31 14:29:05.651 --------------------------------------------------------------------------
. 2018-07-31 14:29:05.651 Using SFTP protocol.
. 2018-07-31 14:29:05.651 Doing startup conversation with host.
. 2018-07-31 14:29:05.652 Session upkeep
. 2018-07-31 14:29:05.652 Looking for network events
. 2018-07-31 14:29:05.652 Detected network event
. 2018-07-31 14:29:05.652 Enumerating network events for socket 1844
. 2018-07-31 14:29:05.652 Enumerated 1 network events making 1 cumulative events for socket 1844
. 2018-07-31 14:29:05.652 Handling network read event on socket 1844 with error 0
. 2018-07-31 14:29:05.652 Server sent command exit status 127
. 2018-07-31 14:29:05.652 Selecting events 0 for socket 1844
. 2018-07-31 14:29:05.652 Disconnected: All channels closed
2018-07-31 14:29:05.783 (EFatal)
I have found that some persons had a solution by changing the SFTP server protocoll options but that has no effect for the issue.
Did I miss something?
From my understanding SFTP only uses the port 22 or is there any other port required?
I have test to access the sftp share on the local LAN in order to check if the firewall or the port forwarding cause the problem. But the problem presist
Sorry for the late reply, I was on a business trip the last weeks.
Indeed I have posted the old logfile and missed to save the right one
But I have just for testing turned on and off the sftp service, and since than it works just fine. The intresting thing is that rebooting the hole server doesn’t solve the issue… (and yes the sftp service was active…)
Maybe I have the chance later to figure out what caused the first issue.
I just ran into this same issue after a fresh install and following the guide for setting up sftp shares. I was pulling my hair out until I read this and then stopped and restarted the sftp service. Connections went from EOF errors using cyberduck and “Connection closed” using Duplicati to magically working. Definitely a bug in adding new sftp shares.