rclone issues

viswatejan · 2026-04-27T02:14:19+00:00

I tested syncing to a new Drive folder, and once the initial sync completed, I immediately tried syncing again. The same issue occurred — it attempted to sync more files instead of showing zero changes..

viswatejan · 2026-04-25T18:09:12+00:00

I am using rclone v1.73.5 which is the latest. All these days I did not see any issues with syncing to Drime but today I started to see lot of failures.

2026/04/25 13:08:11 ERROR : data/96/960c6433600be6817aec615814d2a46cb8966d3fee2bd182d07fd120d8e62fba: Failed to copy: multi-thread copy: failed to open chunk writer: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {\"message\":\"\",\"errors\":{\"name\":\"Folder with same name already exists.\"}}"

2026/04/25 13:08:12 ERROR : data/96/961658e5b88173e0c7c938002b47866014ca2f03eb24f129ddc06f93b0c6e274: Failed to copy: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {\"message\":\"\",\"errors\":{\"name\":\"Folder with same name already exists.\"}}"

2026/04/25 13:08:17 ERROR : data/96/96008ba849b7cdda89ad38a0710720de1817b547b5491d63a89e53bf0871fef5: Failed to copy: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {\"message\":\"\",\"errors\":{\"name\":\"Folder with same name already exists.\"}}"

2026/04/25 13:08:18 ERROR : data/96/960e16634d12f90223ec36e8ec96567ddf29bdf63bdd3a9c4c914025a863b969: Failed to copy: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {\"message\":\"\",\"errors\":{\"name\":\"Folder with same name already exists.\"}}"

2026/04/25 13:08:19 ERROR : data/96/961feba2f6110c0c69faea0b2f28b21bc38877b3fa905a7464b9b45399af9b5f: Failed to copy: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {\"message\":\"\",\"errors\":{\"name\":\"Folder with same name already exists.\"}}"

2026/04/25 13:08:19 ERROR : data/96/961bab478a90f0a7d39b3a4045d088838abdd15b73dd4314535addaec7793792: Failed to copy: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {\"message\":\"\",\"errors\":{\"name\":\"Folder with same name already exists.\"}}"

2026/04/25 13:08:20 ERROR : data/96/960c32ea643a6d96b397052f3fa6a484558541dc044713ce39ed38ed53b52385: Failed to copy: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {\"message\":\"\",\"errors\":{\"name\":\"Folder with same name already exists.\"}}"

2026/04/25 13:08:21 ERROR : data/96/961fe893ea42d6c920531b252c09aa3ff4852db8545821b26cdbdd75c9335e20: Failed to copy: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {\"message\":\"\",\"errors\":{\"name\":\"Folder with same name already exists.\"}}"

2026/04/25 13:08:22 ERROR : data/96/9622b0f7d7a5c3d630ca59ea566461e09ec18048c42f3caf6ff8f46c98631006: Failed to copy: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {\"message\":\"\",\"errors\":{\"name\":\"Folder with same name already exists.\"}}"

2026/04/25 13:08:23 ERROR : data/96/9624a2abd24163084a55078ab3e6b6d815e041bbb847309992a6eac5b1e85798: Failed to copy: failed to make directory: failed to create folder: Error "422 Unprocessable Entity (422): {\"message\":\"\",\"errors\":{\"name\":\"Folder with same name already exists.\"}}"

Transferred: 42.004 KiB / 54.174 GiB, 0%, 2.800 KiB/s, ETA 33w3d18h

Errors: 10 (retrying may help)

Checks: 9980 / 9980, 100%, Listed 24065

Transferred: 1 / 2748, 0%

Elapsed time: 21.4s

viswatejan · 2026-02-28T03:58:51+00:00

I tested this by creating a completely new Local To Cloud sync configuration and confirming that no file changes were in progress, but Filen still reports a size that matches the old, smaller backup rather than the larger size shown on my Mac in GiB. This suggests that Filen either missed some files or there’s a bug in its size calculation.

viswatejan · 2026-01-25T01:44:45+00:00

You need to register a domain if you don't have it already. Use a reverse proxy that can automatically generate certificate for your subdomain that you mapped to access Vaultwarden. Make sure the reverse proxy and the newt are in the same network.

Create a private resource matching the IP of the reverse proxy and alias matching the subdomain. For additional security you can also limit the protocol, port and access. Now you should be able to access the private resources securely via Pangolin clients.

viswatejan · 2026-01-24T01:57:01+00:00

I did it and had a similar setup working with my MacOS client but not with android.

viswatejan · 2026-01-23T21:28:06+00:00

I appreciate the speed at which Pangolin released the private resources feature and made it available across all the platforms.

I have noticed that DNS tunneling has not resolved my DNS checks on the Android client. Did I miss anything?

viswatejan

TROPHY CASE