Release: 2.1.0.109 (Canary) 2025-02-11

[rc36]

Hello,

I finally uninstall 2.1.0.109 and install 2.1.0.108 (<= version without ngclient), and after backup and restore test all is working correctly (I don’t remember the version I had before the update to 2.1.0.109).

I just saw this in the change log of 2.1.0.108 :
"
# New UI
This release contains an updated version of the new UI.
In the url, change ngax to ngclient to try the new UI.
"
But the fact to change as indicated above “ngax” to “ngclient” only done a white sheet.

I will certainly try the next version, maybe in a first time in a virtual machine

[kenkendk]

@ts678

Do ngclient “Restore from config” with no jobs yet

Thanks! I have added an issue for it.

@Taomyn

I just had a thought, that it could be the FQDN of the server not getting looked up for some reason, but then I’m not sure I can replace it because the certificate only contains the FQDN plus the base hostname as an alternate, and I’m not going to add localhost or the IP as alternates to get around that.

I have added an issue for skipping the initial attempts and just jumping straight to the disconnected state. This should make it more resilient to startup issues.

@ts678

Duplicati then takes away permission for me to start it again.

Ok, so there are two reports of this being annoying already, so I think we need to address it.
If we make the feature opt-in, then I estimate that close to 0% of users will apply it.

An alternate solution could be to only set the permissions once, but I am not sure that would be any less annoying overall.

Not sure where to detect the users wants the cross process setup, because it happens after the server has started, and that is the only one that has the permissions to fix it.

Any suggestions for how we could work around this?

@rc36

I selected the new language (for exemple “French”), but there is no difference, the ngclient interface still in english.

We don’t have translation work on the interface yet, so it only affects dates etc for now.

@rc36

I can’t selected a backup version, and then I can’t either select the file or folder to backup.

Thanks for reporting, I have created an issue for this.

@ts678

OK, good to hear NGAX is happy. I’m curious to hear what the devs think ngclient status is now.
I haven’t really done much with it yet. At an earlier mention it was known to be quite incomplete.

We have tested it an found all major functionality to be working. We are aware of places where it does not fully support every quirk from NGAX, but we hope to build something better and not just replicate the functionality.

In the version in 2.1.0.109 there are some issues with Windows paths, but this has been fixed and will be part of 2.1.0.110.

@rc36

Have you the same problem as me about the recovery ? That is to say the impossibility to select a file or a folder to restore due to the absence of a selection windows/menu (as in my screenshot above) ?

I think this was a problem with the dropdowns that was fixed shortly after this build was released.

@rc36

I’m wondering if I should uninstall this version and try to reinstall an older, or wait for a patch.

You can also visit http://localhost:8200/theme.html and set your default “theme” to NGAX. This setting is stored in a cookie that lasts for 90 days.

@rc36

But the fact to change as indicated above “ngax” to “ngclient” only done a white sheet.

In the next canary there will be a button in both ngclient and ngax that allows you to jump to the other interface.