Stopping the configuration does not close access

[maksimkat1]

Even if I stop the AW2 or AW1 configuration, the client can still connect and get VPN access.

[maksimkat1]

Yesterday, after I created a new client configuration in the amneziaVPN application, any clients on the server stopped connecting. After a long investigation, I found the reason in the broken files. Here's what I wrote in a profile chat on amneziavpn:

"Yesterday, as it turned out, the interface of the Amnesia Legacy protocol also fell and did not rise. I didn't realize it right away because I use it only in Kinetics and with a couple of friends (who didn't complain) - but I don't connect on a regular basis. As a result, I went to wg0.conf and clientsTable - and judging by the contents, these files seemed to be cropped. Some of the peers were in one file, but not in the other. As a result, it was easier to recreate the configs in the application, having previously deleted all the relevant ones in the config and everything worked.
I noticed that the broken or cropped lines started with those users (peers) that I "touched" in Amnesia-Web-Panel-Windows (https://github.com/PRVTPRO/Amnezia-Web-Panel ) . this is such a convenient panel where you can centrally monitor the Amnesia servers, manage protocols and users. So - it had the ability to "disable" configs without deleting them. I tried it, but I still had access, so I decided that it didn't work (to close access, I would only have to delete the config). I even wrote issues about it (#64 ). But it looks like this app has made some changes to the config that only showed up yesterday (I was digging a week or two ago).
I have no other explanation. Maybe it's a coincidence again, or maybe not. But I won't go into such panels anymore..."

[PRVTPRO]

I checked the Amnezia protocols. After a user is blocked, their connection is removed from the config, and the user can no longer connect because the configuration is no longer available. This is the expected behavior.

Could you please let me know if the issue still persists on your side?