Release: 2.0.9.107 (Canary) 2024-09-11

Just in case something changed, I tried a small test backup with LZMA (confirmed by 7-Zip).
It worked.

Then we will probably have to see if a developer such as @kenkendk can offer ideas on this.

Is there an option with Tray Icon in white?
With the default macOS Sequoia 15.0 wallpaper, the Tray Icon is barely visible.

Not that I know of, but I donā€™t have a Mac. The main dev does, so maybe this is also waiting.

Did something change in macOS or Duplicati? This topic should cover new 2.0.9.107 issues.

EDIT:

I see you did ask 4 minutes earlier elsewhere, and how you got to the release note youā€™re on:

Thank you for your attention and Iā€™m sorry: Iā€™ve already deleted the question in the other topic.

I tried a fresh install of the CLI version under Ubuntu 24.04.1 LTS. When i try to access the web interface from my windows machine using the provided token i receive a ā€œSignin failed: error tokenā€ message.

The server log shows the following errror:

2024-09-27T18:36:53.969175+02:00 mediabox duplicati-server[1313574]: warn: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[2]
2024-09-27T18:36:53.969204+02:00 mediabox duplicati-server[1313574]:       The response has already started, the error handler will not be executed.
2024-09-27T18:36:53.969243+02:00 mediabox duplicati-server[1313574]: fail: Microsoft.AspNetCore.Server.Kestrel[13]
2024-09-27T18:36:53.969266+02:00 mediabox duplicati-server[1313574]:       Connection id "0HN6V2AC3PD2L", Request id "0HN6V2AC3PD2L:00000001": An unhandled exception was thrown by the application.
2024-09-27T18:36:53.969295+02:00 mediabox duplicati-server[1313574]:       System.InvalidOperationException: Headers are read-only, response has already started.
2024-09-27T18:36:53.969317+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpHeaders.ThrowHeadersReadOnlyException()
2024-09-27T18:36:53.969339+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpResponseHeaders.Microsoft.AspNetCore.Http.IHeaderDictionary.set_ContentType(StringValues value)
2024-09-27T18:36:53.969360+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Http.DefaultHttpResponse.set_ContentType(String value)
2024-09-27T18:36:53.969392+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Http.HttpResponseJsonExtensions.WriteAsJsonAsync[TValue](HttpResponse response, TValue value, JsonTypeInfo`1 jsonTypeInfo, String contentType, CancellationToken cancellationToken)
2024-09-27T18:36:53.969416+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Internal.ExecuteHandlerHelper.WriteJsonResponseAsync[T](HttpResponse response, T value, JsonTypeInfo`1 jsonTypeInfo)
2024-09-27T18:36:53.969438+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Internal.ExecuteHandlerHelper.ExecuteReturnAsync(Object obj, HttpContext httpContext, JsonTypeInfo`1 jsonTypeInfo)
2024-09-27T18:36:53.969462+02:00 mediabox duplicati-server[1313574]:          at lambda_method186(Closure, Object, HttpContext, Object)
2024-09-27T18:36:53.969484+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Http.RequestDelegateFactory.<>c__DisplayClass102_2.<<HandleRequestBodyAndCompileRequestDelegateForJson>b__2>d.MoveNext()
2024-09-27T18:36:53.969505+02:00 mediabox duplicati-server[1313574]:       --- End of stack trace from previous location ---
2024-09-27T18:36:53.969527+02:00 mediabox duplicati-server[1313574]:          at Duplicati.WebserverCore.Middlewares.WebsocketExtensions.<>c__DisplayClass0_0.<<UseNotifications>b__0>d.MoveNext()
2024-09-27T18:36:53.969548+02:00 mediabox duplicati-server[1313574]:       --- End of stack trace from previous location ---
2024-09-27T18:36:53.969571+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.<Invoke>g__Awaited|10_0(ExceptionHandlerMiddlewareImpl middleware, HttpContext context, Task task)
2024-09-27T18:36:53.969592+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.HandleException(HttpContext context, ExceptionDispatchInfo edi)
2024-09-27T18:36:53.969632+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.<Invoke>g__Awaited|10_0(ExceptionHandlerMiddlewareImpl middleware, HttpContext context, Task task)
2024-09-27T18:36:53.969655+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
2024-09-27T18:36:53.969679+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
2024-09-27T18:36:53.969702+02:00 mediabox duplicati-server[1313574]:          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)

type or paste code here

Welcome to the forum @Moritz_P

Doesnā€™t it give a full URL? Does it work from the server that gave it? Are you editing the URL?

Initial signin url: http://localhost:8200/signin.html?token=

I think Iā€™ve tried changing the host before, without luck, but Iā€™m not sure if itā€™s supposed to work.

The developer probably needs to comment.

Can you post an image of it, so people know what youā€™re seeing. My old bad one:

but that was in an extremely early April release, and now things look more like in the manual

image

I suppose while weā€™re waiting for a more expert opinion, we can continue looking at the error. Compact errors are usually sticky (volumes that have too much wasted space stay that way). Because you might want your backup running, you can probably set no-auto-compact so the compact error is suppressed. Note that if thereā€™s really a bad file, restore might also not work.

Add log-file=<path> at log-file-log-level=retry. The live log sometimes does not get everything.

Is the Destination small enough that egress amount would be fine? Iā€™ve been trying to avoid it.

New bug (compared to 2.0.8.1) on Database screen. It doesnā€™t notice no database, so shows

image

instead of

image

Suspected cause is in web server returning 200 OK instead of 404 File or folder not found.

POST /api/v1/filesystem/validate HTTP/1.1
Host: localhost:8200
Connection: keep-alive
Content-Length: 99
Pragma: no-cache
Cache-Control: no-cache
sec-ch-ua-platform: "Windows"
Authorization: Bearer REDACTED
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36 Edg/129.0.0.0
Accept: application/json, text/plain, */*
sec-ch-ua: "Microsoft Edge";v="129", "Not=A?Brand";v="8", "Chromium";v="129"
Content-Type: application/json; charset=UTF-8
sec-ch-ua-mobile: ?0
Origin: http://localhost:8200
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: cors
Sec-Fetch-Dest: empty
Referer: http://localhost:8200/ngax/index.html
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.9
Cookie: default-theme=ngax

{"path":"C:\\Duplicati\\duplicati-2.0.9.107_canary_2024-09-11-win-x64-gui\\RUN\\KZHZDVAHKV.sqlite"}

HTTP/1.1 200 OK
Content-Length: 0
Date: Sat, 28 Sep 2024 12:59:43 GMT
Server: Kestrel

Captura de Tela 2024-09-28 aĢ€s 19.34.04
The white outline in the images (icon) would be more visible.

That looks like my Windows icon before it got fixed. Iā€™m not sure I found the fix, but I did find

In the Beta version I knew in which folder the Tray Icons (.png) were located.
Now in Canary I believe the Tray Icons have been compiled.

I was wondering if you had run the Beta. Although possibly macOS changed since, did icon? Regardless, weā€™ll probably have to wait for comment by developer

If I use a light colored background image in macOS Sequoia the Tray Icon is visible, but if I use a dark colored background image (like the default (Sequoia Sunrise)) the Tray Iconā€™s visibility is poor.

Unfortunatly Ubuntu 24 and NoMachine also have their issues. So, I would need to connect a display to the server first.
But I copied the URL form the server to my windows machine and just replaced ā€œlocalhostā€ with the network name. The URL should be correct.

Iā€™m not sure what that means. Is that what you use or does it fail?

How are you running the test? Is this a LAN or remote, e.g. SSH?

Note that SSH and other remote access tools can forward a port for use by local browser.

Assuming editing is permitted. Still need developer input, but it works better for me today.

Meaning host name? Did you set up the --webservice-allowed-hostnames= to let it in?

Not doing it gave me a different popup than yours though ā€“ Signin failed: Forbidden

Waiting too long gets Signin failed : Signin token expired which you also didnā€™t get.

FWIW I tested in the other direction, browsing from Linux since my Duplicati Windows, but developer input on the error is still probably what weā€™re awaiting to explain your token issue.

Iā€™m still looking for documentation on initial setup which has gotten harder than it used to be.

Documentation on which version to use would be nice too. Have you figured out differences?
Are you doing a CLI start of the Server? If so, maybe you donā€™t need to rely on token access.
Password and other needed things (see help) can be passed in on the startup command line.

I searched the entire Duplicati source, and canā€™t find any spot with the words ā€œerror tokenā€.
Maybe itā€™s in some other code. Is that exactly what it said in a popup in middle of screen?

Hey!

Thanks for you support so far!! The error message was indeed a bit different. I created a new topic for this topic since i think there are multiple discussions going on in parallel here.

I added the parameters you mentioned to the backup job

--run-script-before-required=C:\Windows\duplicati_before.cmd
--run-script-after=C:\Windows\duplicati_after.cmd
--zip-compression-method=LZMA
--zip-compression-zip64=true
--no-auto-compact=true
--log-file=C:\duplicati_LISA_WASABI.log
--log-file-log-level=retry

And I re-ran it - although I did accidentally re-run first with ā€œā€“no-auto-compact=falseā€ as I messed that up. Hopefully other than it taking forever to run hasnā€™t done any further damage, but the second time was quicker and successful.

Iā€™ve attached both the backup job log and the one from the parameter.

Backup.zip (6.1 KB)

Are the logs from the second run? They look successful, so are less interesting for debugging.

The logs from first run (did that fail as usual?) would be relevant. Are those around anywhere?
If not, you can probably make another with a backup or probably even running a Compact now.

Sorry, only the backup job log from the first run, I cleared out the older log between runs and donā€™t have a copy

Backup.zip (3.2 KB)