Hello Vitalie,
thanks for contacting us.
Thank you for the log file.
We reviewed it carefully, and the issue has nothing to do with
TntDrive itself. Your S3-compatible storage server is failing to
handle completely normal S3 operations. The log shows two clear
server-side problems:
- Your storage repeatedly stops responding
There are long sequences of network timeouts such as:
System.Net.WebException: The operation has timed out
These exceptions come directly from the .NET networking stack when the
server simply does not return any response within the required time.
This indicates that your storage is hanging, overloaded, or unable to
process concurrent requests.
- Your storage crashes and returns HTTP 500
At one point your endpoint returns a full ASP.NET runtime error page
instead of a valid S3 response:
500 Internal Server Error / “Runtime Error”
This means the server-side application behind your S3 interface is
failing internally.
When the server manages to respond correctly, everything works:
“Successfully collected files…”
“Successfully received information…”
This confirms that the client side is functioning normally, and the
failures only occur when the storage itself stops responding or
crashes.
Your S3-compatible storage is intermittently unresponsive and
sometimes returns internal server errors. These issues originate
entirely on the storage side and cannot be fixed from the client.
Please forward this information to the support team of your storage
platform so they can investigate the server-side timeouts and
application crashes.
–
Best Regards,
Ivan Moiseev,
TntDrive Team
Netsdk Software
support2@tntdrive.com