To me just glancing at the errors you posted it seems to be credential related but that is just a guess based on this line -

[02.12.2021 15:03:07] <43> Error        Failed to login to host: 'x.x.x.x', port: 2500, elevation to root: 'no', autoSudo: no, use su if sudo fails: no, host name: , IPs: Px.x.x.x], AuthenticationData: tUserName: ubuntu, AuthTypes: ePublicKey]]. The destination would not be a correct SSH server. (System.Exception)

I would also look under the logs to see if those give you any other details.  They are located at - C:\ProgramData\Veeam\Backup -- then the folder related to the Archive Tier offload.

Hello @jmaluna , 

Here are some of my suggestions. You may have configured the SGs and external facing FW. You can see the errors in the log you appended are failed logins.

Is your x.x.x.x (Veeam B&R) a Windows Server or Linux machine? If you are able to answer this correctly, you should be able to resolve this issue. 

• As you can see  from the log, the destination server is not a correct SSH server. (System.Exception)

If this comment helps in resolving your issue, please let us know!

Those error lines are from the logs you mentioned. From one of the proxy appliances log, actually. No more useful information is present.

That Veeam B&R is a Windows server. I’ve tried to uncheck the gateway box to see what happened.

It failed with the same message but different IP address:

d03.12.2021 03:03:33] <53> Info         gLinFLR] Retrying to connect by SSH ...
03.12.2021 03:03:33] <53> Info         Ssh] Creating new connection ce5249ea-770d-4776-9096-5401ba993281 4host: '54.229.168.74', port: 22, elevation to root: 'no', autoSudo: no, use su if sudo fails: no, host name: , IPs: u54.229.168.74], AuthenticationData: 2UserName: ubuntu, AuthTypes: aPublicKey]]].
,03.12.2021 03:03:33] <53> Info         3Ssh] Creating SSH connection ce5249ea-770d-4776-9096-5401ba993281 to server 54.229.168.74
403.12.2021 03:03:33] <53> Info         2Ssh] Creating Granados SSH connection 'ce5249ea-770d-4776-9096-5401ba993281' (unknown protocol)
-03.12.2021 03:03:33] <53> Info         Ssh] logon, host: '54.229.168.74', port: 22, elevation to root: 'no', autoSudo: no, use su if sudo fails: no, host name: , IPs: u54.229.168.74], AuthenticationData: ,UserName: ubuntu, AuthTypes: 8PublicKey]]
i03.12.2021 03:03:33] <53> Info         KSsh] Granados 'ce5249ea-770d-4776-9096-5401ba993281' connected to . Session: sSSH Session; Local: ; Remote: ]
103.12.2021 03:03:54] <53> Error        Failed to connect by SSH. RetryCount: '1'. MaxRetryCount: '10'.
Â03.12.2021 03:03:54] <53> Error        Failed to login to host: '54.229.168.74', port: 22, elevation to root: 'no', autoSudo: no, use su if sudo fails: no, host name: , IPs: a54.229.168.74], AuthenticationData: eUserName: ubuntu, AuthTypes: aPublicKey]]. Unable to establish connection to host 54.229.168.74 on any IP address.

Looking at the proxy appliance logs, it looks like every appliance tried to reach a different IP (probably its own IP or another appliance’s IP address, not sure)

Thank you both for your answers.

So it seems there might be a routing issue?  Unsure since the IP changed but now wondering if it might be DNS possibly?  Can you resolve hosts by both IP and FQDN?  I know with other Veeam technologies if DNS is broke that breaks things.  Would continue to push Support to see what they find though.

Hello @jmaluna, kindly pay attention to some recommendations from @Chris.Childerhose above. Also, the Proxy Appliance requires a connection via SSH and this is correct! Please take a look at this article for a fix to similar issue: 

I hope this helps resolve your issue! 

Hi all,

I finally was able to solve that. EC2 instances created by the proxy appliance were not able to reach the Internet

After that I was facing a certificate download issue that I solved as well. Now I’m facing a permissions issue  

Thank you all!!

Jose Manuel

Great to know that you were able-to configure the rules to allow connectivity! Could you please post the error you are having?

Yeah let us know the permission message and we might be able to assist.

Hi all, solved as well.

I was getting some access denied 403 error when trying to access the archive tier repository.

Our IAM user had S3 full access and EC2 full access permissions but I had to create a custom IAM policy to finally be able to perform the archiving offload.

I’ve used the JSON for inmutable buckets that it is detailed here https://www.veeam.com/kb3151

Regards,

Jose Manuel

Glad to hear you were able to fix it.  Be sure to mark one of the many posts as the answer to your question to help others.

Great to hear! Merry Christmas