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
{"level":"debug","time":"2024-11-15T12:13:46.633","sender":"HTTP","connection_id":"HTTP_csrjluml9mfs73a77t3g","message":"connection removed, local address "172.17.0.8:8080", remote address "192.168.1.185:61174" close fs error: , num open connections: 0"}
Steps to reproduce
1.I have configured the unraid server, and when I log into a client support account, for example, I log in fine, but it issues this log, is this an error? It's red.
Expected behavior
Since the login was successful, this log should not appear in red indicating an error.
SFTPGo version
2.6.2
Data provider
Unraid server
Installation method
Community Docker image
Configuration
config
Relevant log output
No response
What are you using SFTPGo for?
Private user, home usecase (home backup/VPS)
Additional info
No response
The text was updated successfully, but these errors were encountered:
Bug description
{"level":"debug","time":"2024-11-15T12:13:46.633","sender":"HTTP","connection_id":"HTTP_csrjluml9mfs73a77t3g","message":"connection removed, local address "172.17.0.8:8080", remote address "192.168.1.185:61174" close fs error: , num open connections: 0"}
Steps to reproduce
1.I have configured the unraid server, and when I log into a client support account, for example, I log in fine, but it issues this log, is this an error? It's red.
Expected behavior
Since the login was successful, this log should not appear in red indicating an error.
SFTPGo version
2.6.2
Data provider
Unraid server
Installation method
Community Docker image
Configuration
config
Relevant log output
No response
What are you using SFTPGo for?
Private user, home usecase (home backup/VPS)
Additional info
No response
The text was updated successfully, but these errors were encountered: