WHAT IS THE BUG
Client is saying that file upload limit has been reached when it is not.
When checking space information it says that there is still a lot of space available as seen in the following image:
The terminal print of the client looks like this:
09:35:10.669 › {“level”:“WARN”,“ts”:“2023-11-09T09:35:10.668+0100”,“logger”:“filesync”,“msg”:“can’t upload file”,“fileID”:“bafybeigw3kat5rwp47b2yjfa4adfkvdpbp63tmy52o6hfq5toolro3oi3y”,“error”:“file upload limit has been reached”}
{“level”:“WARN”,“ts”:“2023-11-09T09:35:10.668+0100”,“logger”:“filesync”,“msg”:“can’t upload file”,“fileID”:“bafybeigw3kat5rwp47b2yjfa4adfkvdpbp63tmy52o6hfq5toolro3oi3y”,“error”:“file upload limit has been reached”}
Terminal log of any-sync docker compose looks like:
term-log-any-sync.log (127.7 KB)
HOW TO REPRODUCE IT
The files I used for setting up the any-sync server versions of each node are defined in the Dockerfile:
test.zip (7.7 KB)
- To run it change the configurations to the correct ip
- Run docker compose up -d
- Execute the rs-init.sh (Make sure mongosh is installed on local pc)
For the client I used version v0.35.17-beta based on the anytype-heart build with heart.yml in test.zip
THE EXPECTED BEHAVIOR
That the client does sync with any-sync
ADDITIONAL CONTEXT
The server does run behind a vpn but it seems that the communication runs smoothly.
SYSTEM INFORMATION
- laptop with Ubuntu:22.04 for client
- vm running on server with Ubuntu:22.04 for any-sync