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
Context - I'm using SFTPGo as a proxy for clients to gain access to Windows VMs. These clients connect to SFTPGo using standard FTP under a single user, and SFTPGo then connects to those Windows VMs through virtual folders set up for SFTP/SSH. One of my clients is a cron job that accesses a file on one of those VMs once a day at a specified time. The cron job process, my SFTPGo instance, and the Windows VMs are all under the same network.
An issue I'm having is that the FTP file transfer in that cron job fails to execute and I've noticed that when that happens, SFTPGo's logs consistently display an info log detailing access conditions not met for user: \"\" close connection err: <nil>. The strange behavior that I'm noticing is that if I manually trigger that FTP transaction again under the same process as the cron job, it goes through just fine with no access conditions log.
I've tried doing my own homework and taken a look at SFTPGo's source to see what could cause that error and I'm still left stumped as to what could be the reason for it when looking under ActiveConnection.isAccessAllowed(). This issue started happening on June 28th from what I can tell from journalctl. I have verified that the login credentials for the FTP user are correct, and I have doubts that the SFTP/SSH login credentials that SFTPGo is using for the Windows VMs is incorrect given that if I force the same transaction to take place only minutes later, it transfers the file successfully. I'm currently on v2.6.6 6825db7
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Context - I'm using SFTPGo as a proxy for clients to gain access to Windows VMs. These clients connect to SFTPGo using standard FTP under a single user, and SFTPGo then connects to those Windows VMs through virtual folders set up for SFTP/SSH. One of my clients is a cron job that accesses a file on one of those VMs once a day at a specified time. The cron job process, my SFTPGo instance, and the Windows VMs are all under the same network.
An issue I'm having is that the FTP file transfer in that cron job fails to execute and I've noticed that when that happens, SFTPGo's logs consistently display an info log detailing
access conditions not met for user: \"\" close connection err: <nil>. The strange behavior that I'm noticing is that if I manually trigger that FTP transaction again under the same process as the cron job, it goes through just fine with no access conditions log.I've tried doing my own homework and taken a look at SFTPGo's source to see what could cause that error and I'm still left stumped as to what could be the reason for it when looking under
ActiveConnection.isAccessAllowed(). This issue started happening on June 28th from what I can tell from journalctl. I have verified that the login credentials for the FTP user are correct, and I have doubts that the SFTP/SSH login credentials that SFTPGo is using for the Windows VMs is incorrect given that if I force the same transaction to take place only minutes later, it transfers the file successfully. I'm currently on v2.6.6 6825db7Beta Was this translation helpful? Give feedback.
All reactions