Duplicacy Web Restore Folder with Umlaut not working

Hi all,

today I wanted to restore a folder, but this failed (see details below).
Restoring the parent folder works fine. The folder with die umlauts mention below is also restored correctly. The issue applies only if you want to show or restore such a folder directly.

Please describe what you are doing to trigger the bug:

  1. Navigating into to a folder that contains an Umlaut (äöü)
  2. Restoring a folder containing an Umlaut

Please describe what you expect to happen (but doesn’t):

  1. Folder content should be shown
  2. Folder content should be restored

Please describe what actually happens (the wrong behaviour):

  1. Error Message “invalid path” is shown:

  2. No files are restored but “success” message is shown. In the log it looks like the folder is empty (but it is not!):

2021-06-15 21:21:43.149 INFO REPOSITORY_SET Repository set to /Users/markus/Desktop/test
2021-06-15 21:21:43.152 INFO STORAGE_SET Storage set to …
2021-06-15 21:21:43.819 INFO SNAPSHOT_FILTER Loaded 1 include/exclude pattern(s)
2021-06-15 21:21:44.191 INFO RESTORE_INPLACE Forcing in-place mode with a non-default preference path
2021-06-15 21:21:44.704 INFO SNAPSHOT_FILTER Parsing filter file /Users/markus/.duplicacy-web/repositories/localhost/restore/.duplicacy/filters
2021-06-15 21:21:44.704 INFO SNAPSHOT_FILTER Loaded 0 include/exclude pattern(s)
2021-06-15 21:21:44.707 INFO RESTORE_START Restoring /Users/markus/Desktop/test to revision 479
2021-06-15 21:21:44.711 INFO RESTORE_END Restored /Users/markus/Desktop/test to revision 479
2021-06-15 21:21:44.711 INFO RESTORE_STATS Files: 0 total, 0 bytes
2021-06-15 21:21:44.711 INFO RESTORE_STATS Downloaded 0 file, 0 bytes, 0 chunks
2021-06-15 21:21:44.711 INFO RESTORE_STATS Skipped 0 file, 0 bytes
2021-06-15 21:21:44.712 INFO RESTORE_STATS Total running time: 00:00:01

I am using Mac OS 11.4 and duplicacy command line 2.7.2 and web version 1.5.0


I have the same issue when trying to restore files in a folder with non-latin characters. I thought I had a different error in a previously started thread, but it appears I have this error instead.

Any fix here?

For a while I couldn’t reproduce the bug or figure out what went wrong, but now we know the root cause of the issue: Issues with unicode filenames on macOS Safari in Web Edition

The workaround is to use browsers like Chrome or Firefox.

1 Like

Simple workaround! Thank you :blush: