I have an old computer, and in my case it is not surprising that there are errors.
AMD Athlon 300U with Radeon Vega Mobile, Radeon 540X, 8 GB RAM, Win 10 Pro. Fps is kept around 30. The source of the Internet is WiFi. There is also enough disk space.
People with the latest computers are also complaining about this error, which is back today. And it is unclear what determines its appearance in individual players. And I, as the people who wrote above, did not encounter any errors before the 1.25 update.

The error has returned

It's all the same. Moreover, the game servers do not start without a VPN connection. At least for me

I logged into the game in the middle of the day and the error has not appeared until now. It may be a coincidence, but if the same thing happened to other players and the error does not occur in the future, you can exhale

There are many attempts to log in to the server and three throws out of the game Query Timeout

In an attempt to solve this problem, I tried all possible DayZ and computer settings, turned off system protection, changed drivers more than once, reinstalled BattlEye, Dayz, reinstalled Windows three times. I also checked the VPN, restarted the router before each game launch, and created a program to improve the stability of the connection. And either one of these actions helped before the server restart, or it didn't help at all. One of these options could help someone from familiar players, but in my case only the actions of Bohemia will help.

This error appeared after update 1.25. On June 13-14, you released something, as a result of which people were able to play normally. Then on June 20, DayZ updated and downloaded some files, and most of the people with this error had the problem back.
In general, we would like to know how long it will take to solve the problem. And can any actions on our part help us so that BattlEye doesn't kick us out of the game?

I don't understand why this is happening. The developers know how to fix this error - they launched the fix 2 weeks ago. But as a result, we, the players, have been waiting for something incomprehensible for a week now, because they needed to run an untested update that triggers this error.

Эти ошибки снова появились после небольшого патча или фикса этой ночи. Так же с момента изначального появления ошибки Query Timeout некоторые игроки начали жаловаться на проблемы с заходом на сервера в виде ошибки AuthPlayerLoginState

Эти ошибки снова появились после небольшого патча или фикса этой ночи. Так же с момента изначального появления ошибки Query Timeout некоторые игроки начали жаловаться на проблемы с заходом на сервера в виде ошибки AuthPlayerLoginState