#GOOGLE CLOUD WINDOWS FTP SERVER NOT CONNECTING PASSWORD#

#GOOGLE CLOUD WINDOWS FTP SERVER NOT CONNECTING PASSWORD#

Your SFTP password is set up under the SFTP Settings (Settings > SFTP) in your account. Note that this will be different from your Merchant Center password.

Password: the SFTP password you generated in your Merchant Center account.

SFTP server fingerprint: 85:19:8a:fb:60:4b:94:13:5c:ea:fe:3b:99:c7:a5:4d this is the identifying server fingerprint key for.

SFTP server port: 19321 this is the port used by the Google Merchant Center SFTP server.

User: the SFTP username you can find in your Google Merchant Center SFTP settings.

Host name: this is our SFTP server where you will send your feed.

With all of the options, you’ll need the following information: If you haven't used SFTP before, we recommend Option 1 below as it's easiest to configure. While you can use many methods to upload a file via SFTP, we've included instructions for the most common types below. Note: You may only generate a new Google Merchant Center SFTP password you won't be able to retrieve any lost or forgotten passwords.

Click Dismiss to return to the SFTP Settings page.

Make sure you securely store your password before dismissing the popup box. The only solution found for google cloud (for now): to hack the ftp client (in my case it's simple: ruby) forcing the sending of the real external network address in the ftp PORT command.Note: Your password will not be shown again for security reasons. I don't know if in the google environment is possible this kind of solution. The routing device in this example would then forward all traffic for this connection to and from the client address at 192.168.1.2:1930. The remote server would then attempt to connect to 17.254.0.26:1930. When the packet containing this PORT reaches the routing device, it should be rewritten like this, assuming the external address is 17.254.0.26: The device would then have to route the connection incoming from the remote FTP server back to the internal network address of the client. Devices can keep track of FTP data connections, and when a client on a private network uses 'PORT' with an internal network address, the device should dynamically rewrite the packet containing the PORT and IP address and change the address so that it refers to the external IP address of the routing device.

The Solution: The solution depends from the network administrator of the client network to use high-quality network address translation software. The big problem is that when a client program is using network address translation to hide behind a routing device on an internal network, when using PORT the client tells a server on the external network to connect to an address on the client's internal network. I found the solution! Under google cloud network is not possible to establish an active ftp connection with an external ftp server. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 There are no firewall rules in the local machine. The server accept only active mode connections (no passive). In the 'google firewall' I opened all ports from (ftp server address). In my opinion there are some problem in the NAT / port forwarding rules between local and public IP.

I saw another post without any solutions about active mode connection from google cloud. it seems impossible to establish an active ftp connection with an external ftp server.

Running a Google Compute Instance with an internal interface mapped to a temporary public IP.

Google cloud windows ftp server not connecting