Couldn't push gitlab to keyCDN

1

Hello,
After two weeks’ study of goHugo, I could make a Hugo website that I plan to host on keyCDN using a Push Zone with Gitlab.
The pipeline of gitlab fails in the last step,

$ echo 'rsync.keycdn.com,185.172.149.122 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBFM7Jqs3BqC+MSEoVsZ+YMKTjVIMTSKlZX2+0t88o4LZvd+BWt71SkXv4mQ↪ r7xKD59m7jeJcWiO43u7YQzi+Tgg=' >> ~/.ssh/known_hosts
$ echo "${SSH_DEPLOY_KEY}" > ~/.ssh/id_rsa && chmod 600 ~/.ssh/id_rsa
$ rsync -avz --delete --chmod=u=rwX,g=rX public/ ${KEYCDN_USER}@rsync.keycdn.com:zones/${KEYCDN_ZONE_NAME}/
Host key verification failed.
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.2]
ERROR: Job failed: exit code 255

I follow keyCDN’s goHugo deployment manual here, https://www.keycdn.com/support/hugo-hosting/

Could you shine some light on this issue? Thank you.

2

The issue is with connecting to KeyCDN’s server. Maybe it was down for a moment, or their DNS info has changed. That is something you can test out, by using rsync on your local computer, and debugging the connection to their server from there.

If that isn’t an option, you can pass the same snippet you shared here to the support folks at KeyCDN, and they will be able to check into that. :slight_smile:

3

They replied me that the information on that link is outdated.
I will post the latest configuration when everything works well.

4

Just to update in case somebody else is using an outdated rsync command, the updated command should use the following format:

rsync -rtvz --chmod=D2755,F644 --delete public/ ${KEYCDN_USER}@rsync.keycdn.com:${KEYCDN_ZONE_NAME}/

The KeyCDN Hugo hosting article has been updated to reflect this change.

2 Likes