Client v1.10.0 Released

general
1

Features

  • Enhanced user interaction
  • Enhanced UI
  • Autostart on boot
  • Certificate login (you don’t need to enter password anymore)
  • Long live sessions. if you don’t close program, reconnect with in 6 hours without password
2

The version seems to be bugged. With backend 2.0 it connects successfully but after a while (~7-10 minutes) we see the following error and the connection is dropped without any way to reconnect unless you close and reopen agent:

3

With the backend 2.1 that flips between Unknown error and connected. Even if I remove the device posture checks.

image
image621×559 13.1 KB

image
image620×559 11.9 KB

And we see myriad of messages like this about DNS

4

I removed some images because your server public ip was visible.
When client disconnects. Could you check on server

docker ps | grep dns | wc -l

this command will show running dns services. if you have 2 networks. it should be 2. Thanks

1 Like
5

At the same old version clients continue to work with out any problem?

6

Just tried with 1.8.0, getting permanent DNS error
[2024-09-24 19:55:17.282] [error] Error: queryA ENOTFOUND dns.networkname.com
[2024-09-24 19:55:17.895] [info] executing command at worker

I even recreated the whole network as thought there is something with the system DNS and reassigned the services, still the same issue. But this seems to be associated with and update to 2.1 backend which we did today. However, the same issue we got with 2.0 on agent 1.10.

7

image
image701×63 6.14 KB

8

@HKilic I just reverted to agent version 1.9.0 - no problems with backend 2.1, but back to the drive encryption check failure

9

client version(latest) 1.10 with ferrumgate (latest) 2.1, is this works?

10

I regret to say, no.
client version(latest) 1.10 - has DNS error issue

client version 1.9 and ferrumgate (latest) 2.1 - work, however client version 1.9 by itself has an issue with disk encryption check.

Sorry fro bringing the info about 1.9 here in the post of 1.10 but this is only for the sake of clarity. :slight_smile:

11

@HKilic I think I have an idea where the issue is coming from…

Doing some extra checks on 1.10 Agent and 2.1 Backend. Will give you heads up in about 30-40 minutes.

BTW, if that is easier to nail it in discord, I am there as viz.

12

entered to discord. Thanks