Gitlab Host key verification failed

I have a custom post-receive hook in Gitlab to SSH and run some SSH commands. But I’m still receiving this error:

michael@client ~/test $ git push -u origin master
Counting objects: 5, done.
Writing objects: 100% (3/3), 267 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: Updating remote branch /opt/test/master
remote: Host key verification failed.
   6b276dc..89adda9  master -> master
Branch master set up to track remote branch master from origin.



read oldrev newrev refname

BRANCH=`echo $refname | sed -n 's/^refs\/heads\///p'`

if [ "$newrev" -eq 0 ] 2> /dev/null; then
	# branch is being deleted
	echo "Deleting remote branch $SSH_DEST $BRANCH_DIR/$BRANCH"
	echo ssh $SSH_ARGS "$SSH_DEST" /bin/sh
	ssh $SSH_ARGS "$SSH_DEST" /bin/sh <<-EOF
		cd "$BRANCH_DIR" && rm -rf $BRANCH
	# branch is being updated
	echo "Updating remote branch $SSH_DEST $BRANCH_DIR/$BRANCH"
	ssh $SSH_ARGS "$SSH_DEST" /bin/sh <<-EOF
		{ cd "$BRANCH_DIR/$BRANCH" || mkdir -p "$BRANCH_DIR/$BRANCH" && cd "$BRANCH_DIR/$BRANCH"; } \
		&& { git fetch origin && git reset --hard origin/$BRANCH || { git clone "$REPO" ./ && git checkout $BRANCH; }; }

The host key’s are not Changed

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

You are connecting via the SSH protocol. Using SSH, every host has a key. Clients remember the host key associated with a particular address and refuse to connect if a host key appears to change. This prevents man in the middle attacks.

The host key for has changed. If this does not seem fishy to you, you can remove the old key from your local cache using

$ ssh-keygen -R

I strongly encourage you to consider having users authenticate with keys as well. That way, ssh-agent can store key material for convenience (rather than everyone having to enter her password for each connection to the server), and passwords do not go over the network.