Logon after migrating to new computer

1

I just finished migrating Duplicati (https://docs.duplicati.com/configuration-and-management/migrating-duplicati-to-a-new-machin) from a older Raspberry Pi4 setup (circa 2022) to a new Pi4 setup running Trixie.

My migration journey was documented here: How to contact support for new Release questions and extension - #5 by rdk45. Many thanks to @kenkendk and @ts678 as I worked through to process.

So far I have not figured out how to get logged on to the new setup. When I first connected it asked for a “token” which after some searching, I was able to retrieve this via the service status command:

sudo systemctl status duplicati > /mnt/usbdrive/url

which provided a URL with the token. Unfortunately when I tried that I got a “token expired” type message. Further searching seemed to indicate the this command would get me going:

duplicati-server-util login --hosturl=“10.0.1.120:8200” --server-datafolder=/root/.config/Duplicati

it did not and here is the output:

Logging in to the server
Connecting to 10.0.1.120:8200…
System.UriFormatException: Invalid URI: The URI scheme is not valid.
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind, UriCreationOptions& creationOptions)
at System.Uri..ctor(String uriString)
at Duplicati.CommandLine.ServerUtil.Connection.Connect(Settings settings, Boolean obtainRefreshToken, OutputInterceptor console)
at Duplicati.CommandLine.ServerUtil.Commands.Login.<>c.<b__0_0>d.MoveNext()
— End of stack trace from previous location —
at System.CommandLine.NamingConventionBinder.CommandHandler.GetExitCodeAsync(Object returnValue, InvocationContext context)
at System.CommandLine.NamingConventionBinder.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<b__0>d.MoveNext()
— End of stack trace from previous location —
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass17_0.<b__0>d.MoveNext()
— End of stack trace from previous location —
at Duplicati.CommandLine.ServerUtil.Program.<>c.<b__0_1>d.MoveNext()
— End of stack trace from previous location —
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass12_0.<b__0>d.MoveNext()
— End of stack trace from previous location —
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<b__0>d.MoveNext()
— End of stack trace from previous location —
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass19_0.<b__0>d.MoveNext()
— End of stack trace from previous location —
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__18_0>d.MoveNext()
— End of stack trace from previous location —
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<b__0>d.MoveNext()
— End of stack trace from previous location —
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<b__5_0>d.MoveNext()
— End of stack trace from previous location —
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass8_0.<b__0>d.MoveNext()

Here is the content of the /root/.config/Duplicati folder

sudo ls /root/.config/Duplicati
APRSCLEQEE.sqlite ‘backup EOECDKPRXW 20240602080000.sqlite’ Duplicati-server.sqlite IMLMUUZQQD.backup SISXHVXBAO.sqlite
‘backup APRSCLEQEE 20240528080000.sqlite’ ‘backup GKTGHXVRWR 20240601060000.sqlite’ EBZVWXBVIC.sqlite installation.txt
‘backup Duplicati-server 20260716042042.sqlite’ ‘backup QIYWSPFJNT 20240528070001.sqlite’ EOECDKPRXW.sqlite machineid.txt
‘backup EBZVWXBVIC 20240602080000.sqlite’ control_dir_v2 GKTGHXVRWR.sqlite QIYWSPFJNT.sqlite

Can someone get me around this issue? Thanks…RDK

2

Temporary signin token

Note that the sign-in token has a short lifetime to prevent it being used to gain unathorized access from someone who obtains the logs. If the link has expired, simply restart the service or application and a new link will be generated.

Above might be the easier way, but I’ll comment on the other:

From name and --help text, it probably wants a URL:

--hosturl <hosturl> The host URL to use [default: http://127.0.0.1:8200/]

List of URI schemes
I would guess you want http://10.0.1.120:8200, assuming no https.

3

@ts678 SUPER. Got in and set a new password. Found all the older backup configurations which seem to be working. I’m sure I will have additional questions later after I have worked with the new interface and system. But for now - I’m in, working and happy. SOLVED