MatusIvanovic

Hello! This issue is a known situation resulting from the long-term use of SHA1 Certificates on older VA, which the rocky linux VA has disabled as the default state for security reasons (as SHA1 is becoming obsolete) Unfortunately, for a small part of long-term VA users this means their old certs will not be accepted during the login procedure, making it entirely impossible to use the migrated VA. This issue is described, along with steps to fix this issue, on our knowledgebase site https://support.eset.com/en/kb8641-unable-to-log-in-to-eset-protect-web-console-after-migrating-to-a-new-virtual-appliance-rocky-linux Hopefully this'll solve the issue you've ran into.