Just tried out the bewCloud file manager, and it looks pretty good. I managed to get it running nicely on a NanoPi Neo 3 (NPN3) as a docker container. The features are just nice for normal needs. I’ve yet to secure it behind an Apache HTTPS reverse proxy and expose it on the Wild Wild Web, but there’s no doubt it can be done.

The bewCloud-Desktop addon, for Windows at least, is a bit of a bother to get working and access to non local bewCloud servers just didn’t work for me.

• The only allowed connection available to client is to a machine hosted on 127.0.0.1. This is likely to do with browser security which disallows connections to remote servers (CORS?). The initial setup of a sync on the bewCloud-Desktop relies on this connection, and if unsuccessful fails with a rather uninformative error.
• There are two workarounds I’ve tried:

  • Manually add in the Config.json file in /users/xxx/AppData/Roaming/com.bewcloud.sync/ and create the sync entries manually OR

  • Create a local proxy (via ssh perhaps) to map your local IP:port to the remote IP:port. This way the client sees a local host and the allows the connection

  Example of a Config.json file

  {"accounts":[{"remote_directories":["Notes"],"rclone":{"remote_name":"bew4","local_directory":"C:\\synctest"},"last_sync_time":"2025-07-16T22:43:11.279414+00:00"},{"remote_directories":["Photos"],"rclone":{"remote_name":"bew2","local_directory":"C:\\synctest2"},"last_sync_time":"2025-07-16T22:43:11.423726100+00:00"},{"remote_directories":["Directorie"],"rclone":{"remote_name":"bew3","local_directory":"C:\\synctest3"},"last_sync_time":"2025-07-16T22:43:11.630029400+00:00"}]}
  

  The other issue that popped up was the rclone errors are not reported. Rclone sometimes required a –resync between the two file locations, but the error is not reported by the client. Only by recompiling the client in debug mode is a console window presented to assist in debugging. Incidentaly, rclone mentions that bisync is a Beta feature…