File - sFTP from the Cloud ( Google Cloud instance)

Hi all ,

I have a Google Cloud instance running Linux and having a static IP address. I want to use this as sftp server and the source from where ION will pull the csv files for processing in the data flows. We can connect to this instance in 2 ways - password authentication and ssh keys. Unfortunately password authentication is prohibited in the Google Cloud Platform for security purposes. Found KB 2149170 with the required information to proceed . I configured the ssh keys in the instance. There are 4 files generated.

* known_hosts has the host public key in the format ION requires
* id_rsa is your users private key in the format ION requires
* id_rsa.pub
* authorized keys contains the public keys for users

As per the ION guide , Import server public key in openSSH format, with this structure: <modeled host name> <public key type> <public key> . My known_hosts file is in the format as below. I added the hostname and key type to match the format requested by ION.

|1|eRb8RKmY+wiUV34AXKD...............................

When using WinSCP/FileZilla i am able to connect to Google cloud and to update files. But the connection via ION is not getting established. Facing 'HostKey has been changed' exception.

As per Infor support , the sftp setup is out of scope. Any ideas ? Pls help.

Find more posts tagged with

ION Connect

Accepted answers

All comments

Legacy Contributor

This link may help. The error could be that ion has detected a change and you need to allow for that in the known hosts file?

stackabuse.com/.../

Legacy Contributor

It's been a while since I worked on this problem, but I seem to recall needing to generate the PUB file from the actual connection instead of the one I downloaded from the server. Even though I created the PUB key file on the server, it wouldn't work with ION. I had to generate the PUB key file for ION either using SSH or copying from FileZilla. I just remember running into this, and the base cause was the file on the server wasn't what you actually saw when you connected. It was different. I had to download the one presented when connecting.

Legacy Contributor

@manish-miglani ,

manually editing the host file can often cause a problem. if you copy the hoist public key directly from a known_hosts file it should be good 'as is'.

@billy-willoughby is correct in that getting this public key with an actual command line sftp 'connection request' is usually preferable. If you use an app to connect it often hides or encodes or even encrypts the host key making it difficult to determine what it is. so from a terminal, try to sftp to your.sftp.host and (if it's the first time) you'll get a primpt to accept the host key. Once you accept it you can copy it out of your known_hosts file (usually in the users .ssh folder)

I would restate you pattern from:

to:

Take a look at your new host public key:

the "host identifier" might be a hostname or fqdn, an IP address, or a thumbprint... also it can sometimes be multiple comma separated values (e.g. "my.host.name,1.2.3.4")

Also, the encryption type should be "ssh-rsa" at present (afaik) this is the only encryption algorithm supported.

Good luck!

Copyright © 2025 Infor. All rights reserved.