Client 2.1.0 alpha does not even start

[squalou]

Describe the bug

I was just curious about the future 2.0 client so I tried to install it, on a laptop with absolutely no previous defguard config.

Upon start, the client starts a blue screen with "something went wrong"

Error message says

undefined is not an object (evaluating 'r.instances[0].id')

To Reproduce
Steps to reproduce the behavior:

1. add 'release-2.0" APT repository
2. sudo apt install defguard-client (installs 2.1.0)
3. logout / login and start the client
4. See error

Expected behavior

Open a UI to allow some configuration

Version information

• Defguard Core version: not even relevant / not yet installed
• Defguard Gateway version: not even relevant / not yet installed
  • Operating system and version running the gateway: PopOS 24.04
• Your browser and version [e.g. chrome 99, safari]

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

[jakub-tldr]

Hello @squalou,

Could you please run sudo apt update and share the output of commands:

cat /etc/apt/sources.list.d/defguard.list
apt policy defguard defguard-client

Did you add the APT repository exactly as described in the documentation?

Additionally, we’re planning to release the first 2.0 beta in about a week.

[squalou]

Hi, I think I mixed two things when describing the issue.

this is the output when using release 2.0 :

deb [arch=amd64 signed-by=/etc/apt/keyrings/defguard.asc] https://apt.defguard.net/ trixie release-2.0

... for which there is NO client yet, which is expected.

So I did use the pre-release APT repo.

deb [arch=amd64 signed-by=/etc/apt/keyrings/defguard.asc] https://apt.defguard.net/ trixie pre-release-2.0

for which I get

defguard:
  Installed: (none)
  Candidate: 2.1.0-alpha1
  Version table:
     2.1.0-alpha1 500
        500 https://apt.defguard.net trixie/pre-release-2.0 amd64 Packages
     2.0.2-alpha1 500
        500 https://apt.defguard.net trixie/pre-release-2.0 amd64 Packages
     2.0.0-beta2 500
        500 https://apt.defguard.net trixie/pre-release-2.0 amd64 Packages
defguard-client:
  Installed: 2.1.0
  Candidate: 2.1.0
  Version table:
 *** 2.1.0 100
        100 /var/lib/dpkg/status

And it is with this pre-release (defguard-client_2.1.0_amd64.deb) that I got the error.

Sorry for the confusion.

I'll just wait, forget about me ;)

[jakub-tldr]

@squalou
I'm glad that there are no problem with APT. However I'm still worried about that error.

First of all, could you please tell us your OS?

Also, could you please do following:

1. apt remove defguard-client
2. change trixie to bookworm in /etc/apt/sources.list.d/defguard.list
3. apt update
4. apt install defguard-client
5. Run defguard-client

and tell us whether you still see the error?

If yes, please enable debug logging with --log-level debug as described here, and send logs here.

Also, im transfering this issue to https://github.com/DefGuard/client (we have separate repository for desktop client)

[squalou]

Ok ! --log-level debug pointed me to the issue, and to fix it :

Failed to open provisioning configuration file at /home/myuser/.local/share/net.defguard/provisioning.json. Error details: No such file or directory (os error 2)

for some reason, there were some files present there, but incomplete / incoherent.
I removed them all,
started again, and it starts fine now.

I assume the error was from some incomplete files and / or previous format file (should not on this machine but why not, among tests I may have inadvertently installed a 1.6 at one point in time)

BTW : the pre-release-2.0 repo does not suggest client, but pre-release does suggest a 2.0.1 client (be it with bookworm or trixie). Not sure if this is expected.

[squalou]

Well, update after all

• it starts, I can import an existing wireguard tunnel .conf file
• but then in the end the screen is totally blue
• quit / start => error again

 Failed to open provisioning configuration file at /home/myuser/.local/share/net.defguard/provisioning.json. Error details: No such file or directory (os error 2)

This is maybe related to my usecase at the moment I test defguard client against a plain wireguard server.

(Long story short : planning to upgrade from wireguard to defguard in a near future, and trying to establish migration path, so I'm fiddling with different use cases. With 1.6, defguard client managed to work with plain wireguard conf
AND : to your credit, defguard client 1.6 works better for plain wireguard on macos, go wonder :) )