The labels have been updated and the version number has been added to the bottom of all pages. See the new 0.5.0 release.
I updated to 0.5.0 without issue - will let you know if I notice anything wrong.
I deployed duplistatus and added the options in the settings, but nothing arrives in duplicatus
log:
2025-07-11 20:13:18 +02 - [Warning-Duplicati.Library.Modules.Builtin.SendHttpMessage-HttpResponseError]: HTTP Response request failed for: http://192.168.0.121:9666/api/upload
HttpRequestException: Response status code does not indicate success: 400 (Bad Request).,
2025-07-11 20:13:18 +02 - [Warning-Duplicati.Library.Modules.Builtin.ReportHelper-ReportSubmitError]: Failed to send message: System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
]
LimitedErrors: []
Log data:
2025-07-11 20:13:18 +02 - [Warning-Duplicati.Library.Modules.Builtin.SendHttpMessage-HttpResponseError]: HTTP Response request failed for: http://192.168.0.121:9666/api/upload
System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at Duplicati.Library.Modules.Builtin.SendHttpMessage.SendMessage(HttpClient client, SendRequestType target, String subject, String body)
2025-07-11 20:13:18 +02 - [Warning-Duplicati.Library.Modules.Builtin.ReportHelper-ReportSubmitError]: Failed to send message: System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
at Duplicati.Library.Modules.Builtin.SendHttpMessage.SendMessage(String subject, String body)
at Duplicati.Library.Modules.Builtin.ReportHelper.OnFinish(Object result, Exception exception)
When I try to collect backup logs via the gui of duplicatus, I get following error:
Both containers are running on the same host in the same docker network.
I managed to grab the data from my duplicati instance which is running on the same server and docker network.
But connecting to another instance on another server is not working:
duplistatus | 2025-09-10T21:47:23.300691632Z Could not get machine information
duplistatus | 2025-09-10T21:47:23.300769907Z Error collecting backups: Could not get machine information
Hi sir, I have a question, I tried installing via docker with version 0.9.9 or the current latest version, but why is it always stuck in the Starting Process?, I can only use the previous version, please input so I can correct it again. Thanks for the time
Hi wars @wars, the issue is that your Duplicati installation don’t have the machine-id, so the backup collection fails. You have some options:
- check if you find the file machine-id.txt in
/root/.config/Duplicati/or/usr/lib/duplicati/data/if you find it in one but not the other and you have both folders, copymachine-id.txtfrom one to another. If you only have one folder, check it’s contents, it should have a 32-char hex number. - Enter in the Duplicati server new web UI > Settings > Advanced options > +Add advanced option > machine-id and insert a random 32-character hexadecimal. In the old web UI, Settings > Default Options > Add advanced option.
- You can generate a random id using
openssl rand -hex 16in the linux console.
- You can generate a random id using
This will fix the problem.
Hi Sian @sian,
I just released a new version (1.0.1). The startup process was changed in this version. Please give it a try and let me know if you still have issues. If so, please open an issue on GitHub: https://github.com/wsj-br/duplistatus/issues.
Thanks for using Duplistatus.
Nice tool! Currently under testing.
Thanks for sharing!
will try as soon as it’s out on PVE helper scripts
(i dont like docker personally)
A Unraid Docker Template was Awesome: Unraid Template · Issue #56 · wsj-br/duplistatus · GitHub