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
We have a Backup Script that tries to backup to sftp, and we are using this proxy to get the files to s3. While this works quite well, we have a specific setup that seems to fail.
The client tries to access a folder (in the logs you will see that this is /cassandra) and the proxy tries to fetch this folder from s3. S3 returns a 404, and for me it looks like, the proxy now crashes/throws an error.
We have a Backup Script that tries to backup to sftp, and we are using this proxy to get the files to s3. While this works quite well, we have a specific setup that seems to fail.
The client tries to access a folder (in the logs you will see that this is /cassandra) and the proxy tries to fetch this folder from s3. S3 returns a 404, and for me it looks like, the proxy now crashes/throws an error.
This should probably be handled a little better, although I admit, that I am not 100% sure, what the sftp client is issuing.
What is the expected behavior of accessing a folder that does not exist at the moment? Does it behave like a real sftp server in this case?
The text was updated successfully, but these errors were encountered: