Repository gets created without config file

[BartschLabs]

Am I doing something wrong? I just tried creating my second local repository. It gets created on disk, with an obfuscated name and the standard five subfolders, but lacks a config file. The repository creation also seems to complete in Zerobyte. However, I get this error in the log:

info > Initializing restic repository at /media/Backups/E1UL2TNc...
<-- GET /
--> GET / 302 0ms
<-- GET /volumes
--> GET /volumes 200 2ms
error > Restic init failed: 
--> POST /api/v1/repositories 201 24s
<-- GET /api/v1/system/updates
--> GET /api/v1/system/updates 200 2ms
<-- GET /api/v1/system/info
--> GET /api/v1/system/info 200 2ms
<-- GET /__manifest?paths=%2Frepositories%2FE1UL2TNc&version=bbfaf493
--> GET /__manifest?paths=%2Frepositories%2FE1UL2TNc&version=bbfaf493 200 1ms
<-- GET /api/auth/get-session
--> GET /api/auth/get-session 200 3ms
<-- GET /api/v1/repositories/E1UL2TNc
--> GET /api/v1/repositories/E1UL2TNc 200 2ms
<-- GET /api/v1/repositories/8002f441-b4d1-46f6-81d0-5accd4a3cfc9
--> GET /api/v1/repositories/8002f441-b4d1-46f6-81d0-5accd4a3cfc9 200 3ms
<-- GET /api/v1/repositories/8002f441-b4d1-46f6-81d0-5accd4a3cfc9/snapshots
error > Restic snapshots retrieval failed: {"message_type":"exit_error","code":10,"message":"Fatal: repository does not exist: unable to open config file: stat /media/Backups/E1UL2TNc/config: no such file or directory\nIs there a repository at the following location?\n/media/Backups/E1UL2TNc"}

Then I get this error as the Last Error in the repository settings:

Repository not found: The specified repository could not be found. {"message_type":"exit_error","code":10,"message":"Fatal: repository does not exist: unable to open config file: stat /media/Backups/E1UL2TNc/config: no such file or directory\nIs there a repository at the following location?\n/media/Backups/E1UL2TNc"}

The obfuscated name is also a new thing. The first repository I created was created on the disk with the same name I gave it in Zerobyte.

[nicotsx]

Hello, sorry for coming back this late. We had multiple issues about the same thing. This has been fixed by increasing the timeout as it was due to some slow backend not responding fast enough to the default 5s timeout and it would mark it as "created" in zerobyte while it was in fact still not done and killing the command. Please use the latest version and let me know if you still have issues

[BartschLabs]

Thanks, @nicotsx, it's been fixed for me since a recent release.