I’ve been using UrBackup for a couple of years and it’s been running without bigger problems so far. Recently I wanted to add a new client, which can only access the server via internet. This feature wasn’t enabled before on the server.
Since I enabled it, the server started crashing only after running for a few minutes.
The server log only shows this message even after enabling debug mode:
2020-11-17 12:16:02: ERROR: Thread exit with unhandled std::exception bad allocation
2020-11-17 12:16:02: ERROR: Fatal exception code 3765269347 at address 0x00007FFB7A163E49
2020-11-17 12:16:29: ERROR: Fatal exception (APPLICATION CRASHED). Crash dump written to “C:\WINDOWS\TEMP\UrBackup\v2.0.0-20201117-121602-6776-16924.dmp”
2020-11-17 12:16:29: ERROR: Program abort (SIGABRT)
2020-11-17 12:16:29: Authed+capa for client ‘SERVICE’ (encrypted-v2, compressed-zstd, token auth) - 1 spare connections
The server is a version 2.4.13 running on a Windows 10 VM under ESXi. The client is also a Win 10 machine, which is accessing the server via internet. Connection seems to be OK, at least the client says it can reach the server and when I ask for a backup, it starts indexing.
In the server I only configured the internet server name and I left the default port. I enabled doing image & file backups and left the rest of the settings unchanged. Did I miss something, or is this a bug?