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 am using this tool for two plus years. Just had a chance to work with WinSCP/Putty FTP interaction with SFTPGO based SFTP backed with AWS S3.
Although the issue is common, but I am not sure if it has been addressed properly.
While transferring the file to WinSCP, it shows error/warning saying that the file transfer is completed but however, the nopreservetime has to turned off from settings.
I consider since CyberDuck on the other hand doesnt have any kind of these issues, so I thought maybe it can be fixed on sftpgo server side to avoid timestamp issues.
I can provide more details if needed, please do not hesitate to request for that.
Configure SFTP account using SFTPGO server with AWS Backed storage settings
Use CyberDuck to check if a file drop upload works properly which works always
Use WinSCP for same steps to see the dialog box mentioning about the warning
Image as follow
Expected behavior
It can be either ignored by sftpgo server, having an option to silent the warnings like this
Or handle in a way like not to have this issue with timestamps updates
we no longer provide free support sorry. Please check our support policy.
This is the only way to keep the project alive and completely open source.
Thanks for understanding.
Bug description
I am using this tool for two plus years. Just had a chance to work with WinSCP/Putty FTP interaction with SFTPGO based SFTP backed with AWS S3.
Although the issue is common, but I am not sure if it has been addressed properly.
While transferring the file to WinSCP, it shows error/warning saying that the file transfer is completed but however, the nopreservetime has to turned off from settings.
I consider since CyberDuck on the other hand doesnt have any kind of these issues, so I thought maybe it can be fixed on sftpgo server side to avoid timestamp issues.
I can provide more details if needed, please do not hesitate to request for that.
https://winscp.net/forum/viewtopic.php?t=6191
Steps to reproduce
Expected behavior
It can be either ignored by sftpgo server, having an option to silent the warnings like this
Or handle in a way like not to have this issue with timestamps updates
SFTPGo version
2.5.6
Data provider
AWS
Installation method
Community Deb package
Configuration
Relevant log output
No response
What are you using SFTPGo for?
Professional user, 1 person business
Additional info
No response
The text was updated successfully, but these errors were encountered: