Restore file backup stuck at 0%

I’m trying to restore files from the backup server v2.5.33 (Docker) to my Win11 client v2.5.25

When I click on “Restore” a given folder in the web UI I get the confirmation message, then I click Ok and restore process gets stuck at 0%


Relevant log entries from Docker:

2025-05-28 12:17:39: InternetService: Server started up successfully!
2025-05-28 12:17:39: UrBackup Server start up complete.
2025-05-28 12:17:39: Looking for old Sessions... 0 sessions
2025-05-28 12:17:39: Server started up successfully!
2025-05-28 12:17:40: Downloading version file...
2025-05-28 12:17:40: Downloading version file...
2025-05-28 12:17:41: Downloading server version info...
2025-05-28 12:17:41: Downloading dataplan database...
2025-05-28 12:18:09: New Backupclient: Fobos
2025-05-28 12:18:10: FileSRV received 117
2025-05-28 12:18:10: FileSRV received 109
2025-05-28 12:18:10: FileSRV received 109
2025-05-28 12:18:10: FileSRV received 109
2025-05-28 12:18:10: FileSRV received 109
2025-05-28 12:18:10: FileSRV received 109
2025-05-28 12:18:10: FileSRV received 109
2025-05-28 12:18:11: FileSRV received 109
2025-05-28 12:18:11: FileSRV received 109
2025-05-28 12:18:11: FileSRV received 109
2025-05-28 12:18:11: FileSRV received 109
2025-05-28 12:18:11: FileSRV received 109
2025-05-28 12:18:11: FileSRV received 109
2025-05-28 12:18:11: FileSRV received 109
2025-05-28 12:18:11: FileSRV received 109
2025-05-28 12:18:11: FileSRV received 109
2025-05-28 12:18:12: FileSRV received 109
2025-05-28 12:18:12: FileSRV received 109
2025-05-28 12:18:12: FileSRV received 109
2025-05-28 12:18:12: FileSRV received 109
2025-05-28 12:18:12: FileSRV received 109
2025-05-28 12:18:12: FileSRV received 109
2025-05-28 12:18:12: FileSRV received 109
2025-05-28 12:18:12: FileSRV received 109
2025-05-28 12:18:12: FileSRV received 109
2025-05-28 12:18:13: FileSRV received 109
2025-05-28 12:18:13: FileSRV received 109
2025-05-28 12:18:13: FileSRV received 109
2025-05-28 12:18:13: FileSRV received 109
2025-05-28 12:18:13: FileSRV received 109
2025-05-28 12:18:13: FileSRV received 109
2025-05-28 12:18:13: FileSRV received 109
2025-05-28 12:18:13: FileSRV received 109
2025-05-28 12:18:13: FileSRV received 109
2025-05-28 12:18:13: FileSRV received 109
2025-05-28 12:18:14: FileSRV received 109
2025-05-28 12:18:14: FileSRV received 109
2025-05-28 12:18:14: FileSRV received 109
2025-05-28 12:18:14: FileSRV received 109
2025-05-28 12:18:14: FileSRV received 109
2025-05-28 12:18:14: FileSRV received 109
2025-05-28 12:18:14: FileSRV received 109
2025-05-28 12:18:14: FileSRV received 109
2025-05-28 12:18:14: FileSRV received 109
2025-05-28 12:18:15: FileSRV received 109
2025-05-28 12:18:15: FileSRV received 109
2025-05-28 12:18:15: FileSRV received 109
2025-05-28 12:18:15: FileSRV received 109
2025-05-28 12:18:15: FileSRV received 109
2025-05-28 12:18:15: FileSRV received 109
2025-05-28 12:26:34: Starting restore of path "Pictures/Screenshots/". Waiting for client confirmation...
2025-05-28 12:29:52: Starting restore...
2025-05-28 12:29:52: Loading file list...
2025-05-28 12:29:52: FileSRV received 71
2025-05-28 12:29:52: FileSRV received 21
2025-05-28 12:29:52: Calculating download size...
2025-05-28 12:29:52: FileSRV received 109
2025-05-28 12:29:52: Downloading necessary file data...
2025-05-28 12:29:52: FileSRV received 100
2025-05-28 12:29:52: FileSRV received 121

Any help would be greatly appreciated

I’m sorry you are having issues.

To further analyse the problem a client debug log would be useful. The client log file is per default located at C:\Program Files\UrBackup\debug.log on Windows. Run C:\Program Files\UrBackup\enable_debug_logging.bat as admin to enable debug logging. Once debug logging is enabled reproduce the problem.

Attach the log files to your new post or send them to bugreports@urbackup.org because they may contain data which should not be public.

2 Likes

Thank you for your prompt reply!

After reading your post, I tried opening the log file and noticed I had some permission issues. I uninstalled the UrBackup client and reinstalled it as an administrator. It looks like that resolved the problem. :blush:

I’ll keep investigating, but it seems the issue might have been between the keyboard and the chair. :man_facepalming:

1 Like