Hello everyone,
I have deployed a cross region TCP proxy internal load balancer with a front end for every region, when ever I hit my lb endpoint it is resolving both the frontend ip's and changes to another ip apart from one initial one getting error as "host key identification has changed"
Can some one please help me to mitigate this error
Hi @NaveenKota,
Welcome to Google Cloud Community!
This mismatch happens when the host key in the ~/.ssh/known_hosts
file doesn't match the VM's host key. See Host key does not match.
Also, when an IP address changes, a machine is reinstalled or reimaged, a new SSH host key is generated. The old known key needs to be removed from the known_hosts file.
This documentation provides steps to remove all keys from known_host for gLinux & macOS, gWindows, Secure Shell users.
For further reference, you can check this publicly available related forum
See this similar thread can be found on another forum
Let me know if this helps.
Hi @princesslyca ,
Thanks for the insights, Let's suppose my lb endpoint is example.com when I hit that endpoint it resolves to the load balancer front-end ip, for the first time it prompt to accept the host key for the front end ip that it hits for the first time and if it resolves to another ip I am getting this error and also I don't have access to those front-end servers as they are managed by GCP.
The issue of load balancing SSH sessions is very old and very known. What you see is an intended behaviour of SSH implementation. SSH client stores the mapping of the host ip/name to the host key (which is unique for each host). Every time the client sees changes in the mapping it will assume something must have changed and will complain. Your options are: