-
- Enthusiast
- Posts: 32
- Liked: 5 times
- Joined: Nov 26, 2020 3:57 pm
- Full Name: Flavio Santos
- Contact:
v8 new installation - can not add linux proxy
Hello,
I created a brand new server to test, with all default options, and I can not add the Ubuntu proxies I created, I am receiving the following messages:
9/3/2024 7:20:56 PM :: Check proxy connections. Warning: Proxy could not connect to: PostgreSQL,NATS.
9/3/2024 7:20:56 PM :: Install proxy. Error: Could not start the proxy service. Check the backup proxy connection to PostgreSQL and NATS servers. :: 0:00:31
I already checked the firewall and also disabled it to do a test and I had no success.
I did a telnet from the proxy and I can connect to the 5432 and 4222 ports.
I am using Ubunto 20.04.3 LTS, and already blacklisted the "dotnet-"
Any idea?
Thanks!
Flavio Santos.
I created a brand new server to test, with all default options, and I can not add the Ubuntu proxies I created, I am receiving the following messages:
9/3/2024 7:20:56 PM :: Check proxy connections. Warning: Proxy could not connect to: PostgreSQL,NATS.
9/3/2024 7:20:56 PM :: Install proxy. Error: Could not start the proxy service. Check the backup proxy connection to PostgreSQL and NATS servers. :: 0:00:31
I already checked the firewall and also disabled it to do a test and I had no success.
I did a telnet from the proxy and I can connect to the 5432 and 4222 ports.
I am using Ubunto 20.04.3 LTS, and already blacklisted the "dotnet-"
Any idea?
Thanks!
Flavio Santos.
-
- Enthusiast
- Posts: 32
- Liked: 5 times
- Joined: Nov 26, 2020 3:57 pm
- Full Name: Flavio Santos
- Contact:
Re: v8 new installation - can not add linux proxy
We can solve this one, the problem was solved by the HOSTS file. Proxy talk with the VBO server using the server name, not the IP.
My bad.
My bad.
-
- Veeam Software
- Posts: 3476
- Liked: 830 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: v8 new installation - can not add linux proxy
Hi Flavio,
That's correct - proxies and the controller talk using server names, and you need to add those to the file.
Glad that your issue is now resolved!
That's correct - proxies and the controller talk using server names, and you need to add those to the file.
Glad that your issue is now resolved!
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Sep 03, 2019 10:06 am
- Full Name: Felix Grauer
- Contact:
Re: v8 new installation - can not add linux proxy
Hello everyone,
i also had the same issue as flavio, but after i edited the hosts file the connection was not possible. I had to allow file and printer sharing (inbound rule) for ipv4 and i had to disable the windows firewall for private und domain networks. After that i was able to connect to the proxy from my vbo server. Then i enabled the firewall and did a successfull rescan on both of my linux proxy vms.
i also had the same issue as flavio, but after i edited the hosts file the connection was not possible. I had to allow file and printer sharing (inbound rule) for ipv4 and i had to disable the windows firewall for private und domain networks. After that i was able to connect to the proxy from my vbo server. Then i enabled the firewall and did a successfull rescan on both of my linux proxy vms.
-
- Product Manager
- Posts: 8222
- Liked: 1333 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: v8 new installation - can not add linux proxy
@F@Felix22.12
I am not aware of that specific rule that needs to be open. I will investigate and make adjustments to the documentation if needed
I am not aware of that specific rule that needs to be open. I will investigate and make adjustments to the documentation if needed
-
- Novice
- Posts: 7
- Liked: 3 times
- Joined: Dec 18, 2024 1:24 pm
- Full Name: Ronny Pot
- Contact:
Re: v8 new installation - can not add linux proxy
Thanks had the same issue and needed to add the Veeam server to the Linux host file
-
- Enthusiast
- Posts: 84
- Liked: 12 times
- Joined: Aug 21, 2018 5:33 am
- Contact:
Re: v8 new installation - can not add linux proxy
same problem here : spent the whole day trying to connect VBO (windows server 2022) to a linux ubuntu (22.04 or 24.04) proxy.
no success, I will have to open a ticket and loose more time for something that "should" be trivial
here is the last atempt logged :
no success, I will have to open a ticket and loose more time for something that "should" be trivial
here is the last atempt logged :
Code: Select all
[03.01.2025 17:35:58.466] 31 (1) Validating connection to server 10.12.29.236...
[03.01.2025 17:35:58.466] 31 (1) Establishing SSH Rebex connection to host: 10.12.29.236 (ID: 94be7e1d-5378-4815-a0d8-c46b4992a1c9)...
[03.01.2025 17:35:58.468] 31 (1) Warning: Failed to create Rebex (DSS/RSA) SSH connection. Switching to Renci SSH...
[03.01.2025 17:35:58.469] 31 (1) Warning: Negotiation failed. The client and the server have no common host key algorithm. Server supports 'rsa-sha2-512' which is not enabled at the client.
[03.01.2025 17:35:58.469] 31 (1) Type: Rebex.Net.SshException
[03.01.2025 17:35:58.469] 31 (1) Stack:
[03.01.2025 17:35:58.469] 31 (1) at Rebex.Net.Ssh.qvwcl(String p0, Int32 p1, SshParameters p2, zmezg p3)
[03.01.2025 17:35:58.469] 31 (1) at Veeam.SSH.Core.RebexSSHLib.SshRebexConnector.EstablishConnection(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator fingerprintChecker, Guid connectionId, SshRebexAuthenticator authenticator, String[] customHostKeyAlgorithms, ILogger logger, RebexSshClient& sshClient)
[03.01.2025 17:35:58.469] 31 (1) at Veeam.SSH.Core.RebexSSHLib.SshRebexConnectionImpl.<>c__DisplayClass14_0.<CreateEmulatingGranados>b__0(SshRebexConnectionImpl& impl)
[03.01.2025 17:35:58.469] 31 (1) at Veeam.Core.Memory.Disposable.Create[TValue](CreateAction`1 createInstance)
[03.01.2025 17:35:58.469] 31 (1) at Veeam.SSH.Core.SshConnection.CreateConnectionImpl(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator sshTargetHostFingerprintValidator, ISshTransportEventsListener transportListener, ILogger logger)
[03.01.2025 17:35:58.469] 31 (1) SshStatus: OperationFailure
[03.01.2025 17:35:58.469] 31 (1) SshRemote: False
[03.01.2025 17:35:58.469] 31 (1) Status: OperationFailure
[03.01.2025 17:35:58.469] 31 (1) ProtocolCode: 0
[03.01.2025 17:35:58.469] 31 (1) ProtocolMessage: Unspecified
[03.01.2025 17:35:58.469] 31 (1) Warning: The client and the server have no common host key algorithm.
[03.01.2025 17:35:58.469] 31 (1) Type: Rebex.Net.SshException
[03.01.2025 17:35:58.469] 31 (1) Stack:
[03.01.2025 17:35:58.469] 31 (1) at ioqcn.shwed.scjzn(fblfl p0, SshKeyExchangeAlgorithm p1, SshHostKeyAlgorithm p2, pnrbh p3, pnrbh p4, ubycw p5, ubycw p6)
[03.01.2025 17:35:58.469] 31 (1) at Rebex.Net.SshSession.pfylg(Byte[] p0)
[03.01.2025 17:35:58.469] 31 (1) at Rebex.Net.SshSession.Negotiate()
[03.01.2025 17:35:58.469] 31 (1) at Rebex.Net.Ssh.tgdur.zsblg(zmezg p0, Boolean p1)
[03.01.2025 17:35:58.469] 31 (1) at Rebex.Net.Ssh.qvwcl(String p0, Int32 p1, SshParameters p2, zmezg p3)
[03.01.2025 17:35:58.469] 31 (1) SshStatus: OperationFailure
[03.01.2025 17:35:58.469] 31 (1) SshRemote: False
[03.01.2025 17:35:58.469] 31 (1) Status: OperationFailure
[03.01.2025 17:35:58.469] 31 (1) ProtocolCode: 3
[03.01.2025 17:35:58.469] 31 (1) ProtocolMessage: KeyExchangeFailed
[03.01.2025 17:35:58.469] 31 (1) SshServerInfo: Rebex.Net.SshServerInfo
[03.01.2025 17:35:58.469] 31 (1) Establishing SSH Renci connection to host: 10.12.29.236...
[03.01.2025 17:35:58.474] 27 (1) Validating SSH public key...
[03.01.2025 17:35:58.474] 27 (1) Expected:
[03.01.2025 17:35:58.474] 27 (1) Received server key: AAAAC3NzaC1lZDI1NTE5AAAAIGIjodVxFRIcimmjOEDP5DNoTC7o1vWc8PWtxWFjLD+x
[03.01.2025 17:35:58.474] 31 (1) Disconnecting from: 10.12.29.236...
[03.01.2025 17:35:58.474] 31 (1) disconnected.
[03.01.2025 17:35:58.474] 31 (1) Warning: Failed to validate access to the server.
[03.01.2025 17:35:58.474] 31 (1) Warning: Failed to validate 10.12.29.236 fingerprint. Additional information from the Mount service: A public key was not passed to the validator. Cannot validate the public key from the server.
[03.01.2025 17:35:58.474] 31 (1) Type: Veeam.Core.Security.FingerprintCheckFailedException
[03.01.2025 17:35:58.474] 31 (1) Stack:
[03.01.2025 17:35:58.474] 31 (1) at Veeam.SSH.Core.RenciSSHLib.RenciFingerprintChecker.VerifyHostKey(Object sender, HostKeyEventArgs e)
[03.01.2025 17:35:58.474] 31 (1) at Renci.SshNet.Security.KeyExchange.ValidateExchangeHash(Byte[] encodedKey, Byte[] encodedSignature)
[03.01.2025 17:35:58.474] 31 (1) at Renci.SshNet.Security.KeyExchange.Finish()
[03.01.2025 17:35:58.474] 31 (1) at Renci.SshNet.Security.KeyExchangeECCurve25519.Finish()
[03.01.2025 17:35:58.474] 31 (1) at Renci.SshNet.Session.MessageListener()
[03.01.2025 17:35:58.474] 31 (1) --- End of stack trace from previous location ---
[03.01.2025 17:35:58.474] 31 (1) at Renci.SshNet.Session.WaitOnHandle(WaitHandle waitHandle, TimeSpan timeout)
[03.01.2025 17:35:58.474] 31 (1) at Renci.SshNet.Session.Connect()
[03.01.2025 17:35:58.474] 31 (1) at Renci.SshNet.BaseClient.CreateAndConnectSession()
[03.01.2025 17:35:58.474] 31 (1) at Renci.SshNet.BaseClient.Connect()
[03.01.2025 17:35:58.474] 31 (1) at Veeam.SSH.Core.RenciLib.SshClientConnectionFactory.<>c__DisplayClass0_0.<CreateConnectedSshClient>g__CreateInstance|0(SshClient& sshClient)
[03.01.2025 17:35:58.474] 31 (1) at Veeam.Core.Memory.Disposable.Create[TValue](CreateAction`1 createInstance)
[03.01.2025 17:35:58.474] 31 (1) at Veeam.SSH.Core.RenciLib.SshRenciConnectionImpl.Connect()
[03.01.2025 17:35:58.474] 31 (1) at Veeam.Core.Memory.Disposable.Create[TValue](CreateAction`1 createInstance)
[03.01.2025 17:35:58.474] 31 (1) at Veeam.SSH.Core.SshConnection.CreateConnectionImpl(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator sshTargetHostFingerprintValidator, ISshTransportEventsListener transportListener, ILogger logger)
[03.01.2025 17:35:58.474] 31 (1) at Veeam.SSH.Core.SshConnectionCreator.Create(ISshConnectionConfig spec, ISshTargetHostFingerprintValidator sshTargetHostFingerprintValidator, ISshTransportEventsListener transportEventsListener, ILogger logger, String tempFolderPath, CancellationToken cancellationToken, Nullable`1 connectionRetryInterval, Nullable`1 connectionRetryCount)
[03.01.2025 17:35:58.474] 31 (1) at Veeam.Linux.Client.LinuxHostConnection.Connect()
[03.01.2025 17:35:58.474] 31 (1) at Veeam.Linux.Client.LinuxHostConnection.Execute(ILinuxCommand command)
[03.01.2025 17:35:58.474] 31 (1) at Veeam.Linux.Client.LinuxHostConnection.GetShellType()
[03.01.2025 17:35:58.474] 31 (1) at Veeam.Linux.Client.LinuxHostConnection.OpenShell()
[03.01.2025 17:35:58.474] 31 (1) at Veeam.Linux.Client.Validators.LinuxServerAccessValidator.CheckConnection(ILinuxConnectionConfig connectionConfig, ISshTargetHostFingerprintValidator sshTargetHostFingerprintValidator, ILogger logger, CancellationToken cancellationToken, Boolean& isRootAccount, Boolean& elevateToRootNotNeeded)
[03.01.2025 17:35:58.474] 31 (1) at Veeam.Linux.Client.Validators.LinuxServerAccessValidator.ValidateInternal(ILinuxConnectionConfig connectionConfig, Boolean isRootRequired, ISshTargetHostFingerprintValidator targetHostFingerprintValidator, ILogger logger, CancellationToken cancellationToken, Boolean& elevateToRootNotNeeded)
[03.01.2025 17:35:58.474] 31 (1) at Veeam.Linux.Client.Validators.LinuxServerAccessValidator.Validate(ILinuxConnectionConfig connectionConfig, ILogger logger, Boolean& elevateToRootNotNeeded, CancellationToken cancellationToken, Boolean isRootRequired, ISshTargetHostFingerprintValidator targetHostFingerprintValidator)
[03.01.2025 17:35:59.797] 31 (1) Validating connection to server 10.12.29.236...
[03.01.2025 17:35:59.797] 31 (1) Establishing SSH Rebex connection to host: 10.12.29.236 (ID: b253b9ae-ebd8-4460-a874-a9de9b31570a)...
[03.01.2025 17:35:59.799] 31 (1) Warning: Failed to create Rebex (DSS/RSA) SSH connection. Switching to Renci SSH...
[03.01.2025 17:35:59.800] 31 (1) Warning: Negotiation failed. The client and the server have no common host key algorithm. Server supports 'rsa-sha2-512' which is not enabled at the client.
[03.01.2025 17:35:59.800] 31 (1) Type: Rebex.Net.SshException
[03.01.2025 17:35:59.800] 31 (1) Stack:
[03.01.2025 17:35:59.800] 31 (1) at Rebex.Net.Ssh.qvwcl(String p0, Int32 p1, SshParameters p2, zmezg p3)
[03.01.2025 17:35:59.800] 31 (1) at Veeam.SSH.Core.RebexSSHLib.SshRebexConnector.EstablishConnection(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator fingerprintChecker, Guid connectionId, SshRebexAuthenticator authenticator, String[] customHostKeyAlgorithms, ILogger logger, RebexSshClient& sshClient)
[03.01.2025 17:35:59.800] 31 (1) at Veeam.SSH.Core.RebexSSHLib.SshRebexConnectionImpl.<>c__DisplayClass14_0.<CreateEmulatingGranados>b__0(SshRebexConnectionImpl& impl)
[03.01.2025 17:35:59.800] 31 (1) at Veeam.Core.Memory.Disposable.Create[TValue](CreateAction`1 createInstance)
[03.01.2025 17:35:59.800] 31 (1) at Veeam.SSH.Core.SshConnection.CreateConnectionImpl(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator sshTargetHostFingerprintValidator, ISshTransportEventsListener transportListener, ILogger logger)
[03.01.2025 17:35:59.800] 31 (1) SshStatus: OperationFailure
[03.01.2025 17:35:59.800] 31 (1) SshRemote: False
[03.01.2025 17:35:59.800] 31 (1) Status: OperationFailure
[03.01.2025 17:35:59.800] 31 (1) ProtocolCode: 0
[03.01.2025 17:35:59.800] 31 (1) ProtocolMessage: Unspecified
[03.01.2025 17:35:59.800] 31 (1) Warning: The client and the server have no common host key algorithm.
[03.01.2025 17:35:59.800] 31 (1) Type: Rebex.Net.SshException
[03.01.2025 17:35:59.800] 31 (1) Stack:
[03.01.2025 17:35:59.800] 31 (1) at ioqcn.shwed.scjzn(fblfl p0, SshKeyExchangeAlgorithm p1, SshHostKeyAlgorithm p2, pnrbh p3, pnrbh p4, ubycw p5, ubycw p6)
[03.01.2025 17:35:59.800] 31 (1) at Rebex.Net.SshSession.pfylg(Byte[] p0)
[03.01.2025 17:35:59.800] 31 (1) at Rebex.Net.SshSession.Negotiate()
[03.01.2025 17:35:59.800] 31 (1) at Rebex.Net.Ssh.tgdur.zsblg(zmezg p0, Boolean p1)
[03.01.2025 17:35:59.800] 31 (1) at Rebex.Net.Ssh.qvwcl(String p0, Int32 p1, SshParameters p2, zmezg p3)
[03.01.2025 17:35:59.800] 31 (1) SshStatus: OperationFailure
[03.01.2025 17:35:59.800] 31 (1) SshRemote: False
[03.01.2025 17:35:59.800] 31 (1) Status: OperationFailure
[03.01.2025 17:35:59.800] 31 (1) ProtocolCode: 3
[03.01.2025 17:35:59.800] 31 (1) ProtocolMessage: KeyExchangeFailed
[03.01.2025 17:35:59.800] 31 (1) SshServerInfo: Rebex.Net.SshServerInfo
[03.01.2025 17:35:59.800] 31 (1) Establishing SSH Renci connection to host: 10.12.29.236...
[03.01.2025 17:35:59.804] 81 (1) Validating SSH public key...
[03.01.2025 17:35:59.804] 81 (1) Expected: AAAAC3NzaC1lZDI1NTE5AAAAIGIjodVxFRIcimmjOEDP5DNoTC7o1vWc8PWtxWFjLD+x
[03.01.2025 17:35:59.804] 81 (1) Received server key: AAAAC3NzaC1lZDI1NTE5AAAAIGIjodVxFRIcimmjOEDP5DNoTC7o1vWc8PWtxWFjLD+x
[03.01.2025 17:35:59.813] 31 (1) successfully connected
[03.01.2025 17:35:59.813] 31 (1) Created SSH connection implementation type: SshRenciConnectionImpl.
[03.01.2025 17:35:59.813] 31 (1) Executing: \echo $SHELL...
[03.01.2025 17:35:59.858] 31 (1) SSH output: /bin/bash
[03.01.2025 17:35:59.858] 31 (1) Opening shell: 21...
[03.01.2025 17:35:59.858] 31 (1) Establishing SSH Rebex connection to host: 10.12.29.236 (ID: 37f07272-cf58-417c-9e7b-c0571ce63204)...
[03.01.2025 17:35:59.859] 31 (1) Warning: Failed to create Rebex (DSS/RSA) SSH connection. Switching to Renci SSH...
[03.01.2025 17:35:59.860] 31 (1) Warning: Negotiation failed. The client and the server have no common host key algorithm. Server supports 'rsa-sha2-512' which is not enabled at the client.
[03.01.2025 17:35:59.860] 31 (1) Type: Rebex.Net.SshException
[03.01.2025 17:35:59.860] 31 (1) Stack:
[03.01.2025 17:35:59.860] 31 (1) at Rebex.Net.Ssh.qvwcl(String p0, Int32 p1, SshParameters p2, zmezg p3)
[03.01.2025 17:35:59.860] 31 (1) at Veeam.SSH.Core.RebexSSHLib.SshRebexConnector.EstablishConnection(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator fingerprintChecker, Guid connectionId, SshRebexAuthenticator authenticator, String[] customHostKeyAlgorithms, ILogger logger, RebexSshClient& sshClient)
[03.01.2025 17:35:59.860] 31 (1) at Veeam.SSH.Core.RebexSSHLib.SshRebexConnectionImpl.<>c__DisplayClass14_0.<CreateEmulatingGranados>b__0(SshRebexConnectionImpl& impl)
[03.01.2025 17:35:59.860] 31 (1) at Veeam.Core.Memory.Disposable.Create[TValue](CreateAction`1 createInstance)
[03.01.2025 17:35:59.860] 31 (1) at Veeam.SSH.Core.SshConnection.CreateConnectionImpl(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator sshTargetHostFingerprintValidator, ISshTransportEventsListener transportListener, ILogger logger)
[03.01.2025 17:35:59.860] 31 (1) SshStatus: OperationFailure
[03.01.2025 17:35:59.860] 31 (1) SshRemote: False
[03.01.2025 17:35:59.860] 31 (1) Status: OperationFailure
[03.01.2025 17:35:59.860] 31 (1) ProtocolCode: 0
[03.01.2025 17:35:59.860] 31 (1) ProtocolMessage: Unspecified
[03.01.2025 17:35:59.860] 31 (1) Warning: The client and the server have no common host key algorithm.
[03.01.2025 17:35:59.860] 31 (1) Type: Rebex.Net.SshException
[03.01.2025 17:35:59.860] 31 (1) Stack:
[03.01.2025 17:35:59.860] 31 (1) at ioqcn.shwed.scjzn(fblfl p0, SshKeyExchangeAlgorithm p1, SshHostKeyAlgorithm p2, pnrbh p3, pnrbh p4, ubycw p5, ubycw p6)
[03.01.2025 17:35:59.860] 31 (1) at Rebex.Net.SshSession.pfylg(Byte[] p0)
[03.01.2025 17:35:59.860] 31 (1) at Rebex.Net.SshSession.Negotiate()
[03.01.2025 17:35:59.860] 31 (1) at Rebex.Net.Ssh.tgdur.zsblg(zmezg p0, Boolean p1)
[03.01.2025 17:35:59.860] 31 (1) at Rebex.Net.Ssh.qvwcl(String p0, Int32 p1, SshParameters p2, zmezg p3)
[03.01.2025 17:35:59.860] 31 (1) SshStatus: OperationFailure
[03.01.2025 17:35:59.860] 31 (1) SshRemote: False
[03.01.2025 17:35:59.860] 31 (1) Status: OperationFailure
[03.01.2025 17:35:59.860] 31 (1) ProtocolCode: 3
[03.01.2025 17:35:59.860] 31 (1) ProtocolMessage: KeyExchangeFailed
[03.01.2025 17:35:59.860] 31 (1) SshServerInfo: Rebex.Net.SshServerInfo
[03.01.2025 17:35:59.860] 31 (1) Establishing SSH Renci connection to host: 10.12.29.236...
[03.01.2025 17:35:59.864] 89 (1) Validating SSH public key...
[03.01.2025 17:35:59.864] 89 (1) Expected: AAAAC3NzaC1lZDI1NTE5AAAAIGIjodVxFRIcimmjOEDP5DNoTC7o1vWc8PWtxWFjLD+x
[03.01.2025 17:35:59.864] 89 (1) Received server key: AAAAC3NzaC1lZDI1NTE5AAAAIGIjodVxFRIcimmjOEDP5DNoTC7o1vWc8PWtxWFjLD+x
[03.01.2025 17:35:59.873] 31 (1) successfully connected
[03.01.2025 17:35:59.873] 31 (1) Created SSH connection implementation type: SshRenciConnectionImpl.
[03.01.2025 17:35:59.925] 89 (1) Warning: Unexpected SSH output: proxy1@veeamproxyvbo1:~$
[03.01.2025 17:35:59.925] 31 (1) Executing [21]: \export PS1="\[Veeam> \]"...
[03.01.2025 17:35:59.926] 89 (1) SSH output [21]: [?2004l
[03.01.2025 17:35:59.926] 31 (1) [?2004hVeeam>
[03.01.2025 17:35:59.926] 31 (1) Executing [21]: \stty -echo...
[03.01.2025 17:35:59.926] 89 (1) SSH output [21]: [?2004l
[03.01.2025 17:35:59.927] 31 (1) [?2004hVeeam>
[03.01.2025 17:35:59.927] 31 (1) Executing [21]: \bind 'set enable-bracketed-paste off'...
[03.01.2025 17:35:59.927] 89 (1) SSH output [21]: [?2004l
[03.01.2025 17:35:59.927] 31 (1) Veeam>
[03.01.2025 17:35:59.927] 31 (1) Executing [21]: echo test;...
[03.01.2025 17:35:59.927] 89 (1) SSH output [21]: test
[03.01.2025 17:35:59.927] 31 (1) Veeam>
[03.01.2025 17:35:59.927] 31 (1) Executing [21]: \unalias -a...
[03.01.2025 17:35:59.927] 31 (1) Veeam>
[03.01.2025 17:35:59.927] 31 (1) Executing [21]: locale -a | \grep en_US.utf8...
[03.01.2025 17:35:59.929] 89 (1) SSH output [21]: en_US.utf8
[03.01.2025 17:35:59.929] 31 (1) Veeam>
[03.01.2025 17:35:59.929] 31 (1) Executing [21]: export NLS_LANG=AMERICAN_AMERICA...
[03.01.2025 17:35:59.929] 31 (1) Veeam>
[03.01.2025 17:35:59.929] 31 (1) Executing [21]: echo $?...
[03.01.2025 17:35:59.929] 89 (1) SSH output [21]: 0
[03.01.2025 17:35:59.929] 31 (1) Veeam>
[03.01.2025 17:35:59.929] 31 (1) Executing [21]: export LC_ALL=en_US.UTF-8...
[03.01.2025 17:35:59.930] 31 (1) Veeam>
[03.01.2025 17:35:59.930] 31 (1) Executing [21]: echo $?...
[03.01.2025 17:35:59.930] 89 (1) SSH output [21]: 0
[03.01.2025 17:35:59.930] 31 (1) Veeam>
[03.01.2025 17:35:59.930] 31 (1) Executing [21]: id -u 'proxy1'...
[03.01.2025 17:35:59.931] 89 (1) SSH output [21]: 1000
[03.01.2025 17:35:59.931] 31 (1) Veeam>
[03.01.2025 17:35:59.931] 31 (1) Executing [21]: echo $?...
[03.01.2025 17:35:59.931] 89 (1) SSH output [21]: 0
[03.01.2025 17:35:59.931] 31 (1) Veeam>
[03.01.2025 17:35:59.931] 31 (1) Closing shell: 21...
[03.01.2025 17:35:59.932] 31 (1) Disconnecting from: 10.12.29.236...
[03.01.2025 17:35:59.932] 31 (1) disconnected.
[03.01.2025 17:35:59.932] 31 (1) Disconnecting from: 10.12.29.236...
[03.01.2025 17:35:59.932] 31 (1) disconnected.
[03.01.2025 17:35:59.932] 31 (1) Establishing SSH Rebex connection to host: 10.12.29.236 (ID: 9a1de1c7-9297-4a38-8fc1-2447d2251f47)...
[03.01.2025 17:35:59.934] 31 (1) Warning: Failed to create Rebex (DSS/RSA) SSH connection. Switching to Renci SSH...
[03.01.2025 17:35:59.934] 31 (1) Warning: Negotiation failed. The client and the server have no common host key algorithm. Server supports 'rsa-sha2-512' which is not enabled at the client.
[03.01.2025 17:35:59.934] 31 (1) Type: Rebex.Net.SshException
[03.01.2025 17:35:59.934] 31 (1) Stack:
[03.01.2025 17:35:59.934] 31 (1) at Rebex.Net.Ssh.qvwcl(String p0, Int32 p1, SshParameters p2, zmezg p3)
[03.01.2025 17:35:59.934] 31 (1) at Veeam.SSH.Core.RebexSSHLib.SshRebexConnector.EstablishConnection(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator fingerprintChecker, Guid connectionId, SshRebexAuthenticator authenticator, String[] customHostKeyAlgorithms, ILogger logger, RebexSshClient& sshClient)
[03.01.2025 17:35:59.934] 31 (1) at Veeam.SSH.Core.RebexSSHLib.SshRebexConnectionImpl.<>c__DisplayClass14_0.<CreateEmulatingGranados>b__0(SshRebexConnectionImpl& impl)
[03.01.2025 17:35:59.934] 31 (1) at Veeam.Core.Memory.Disposable.Create[TValue](CreateAction`1 createInstance)
[03.01.2025 17:35:59.934] 31 (1) at Veeam.SSH.Core.SshConnection.CreateConnectionImpl(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator sshTargetHostFingerprintValidator, ISshTransportEventsListener transportListener, ILogger logger)
[03.01.2025 17:35:59.934] 31 (1) SshStatus: OperationFailure
[03.01.2025 17:35:59.934] 31 (1) SshRemote: False
[03.01.2025 17:35:59.934] 31 (1) Status: OperationFailure
[03.01.2025 17:35:59.934] 31 (1) ProtocolCode: 0
[03.01.2025 17:35:59.934] 31 (1) ProtocolMessage: Unspecified
[03.01.2025 17:35:59.934] 31 (1) Warning: The client and the server have no common host key algorithm.
[03.01.2025 17:35:59.934] 31 (1) Type: Rebex.Net.SshException
[03.01.2025 17:35:59.934] 31 (1) Stack:
[03.01.2025 17:35:59.934] 31 (1) at ioqcn.shwed.scjzn(fblfl p0, SshKeyExchangeAlgorithm p1, SshHostKeyAlgorithm p2, pnrbh p3, pnrbh p4, ubycw p5, ubycw p6)
[03.01.2025 17:35:59.934] 31 (1) at Rebex.Net.SshSession.pfylg(Byte[] p0)
[03.01.2025 17:35:59.934] 31 (1) at Rebex.Net.SshSession.Negotiate()
[03.01.2025 17:35:59.934] 31 (1) at Rebex.Net.Ssh.tgdur.zsblg(zmezg p0, Boolean p1)
[03.01.2025 17:35:59.934] 31 (1) at Rebex.Net.Ssh.qvwcl(String p0, Int32 p1, SshParameters p2, zmezg p3)
[03.01.2025 17:35:59.934] 31 (1) SshStatus: OperationFailure
[03.01.2025 17:35:59.934] 31 (1) SshRemote: False
[03.01.2025 17:35:59.934] 31 (1) Status: OperationFailure
[03.01.2025 17:35:59.934] 31 (1) ProtocolCode: 3
[03.01.2025 17:35:59.934] 31 (1) ProtocolMessage: KeyExchangeFailed
[03.01.2025 17:35:59.934] 31 (1) SshServerInfo: Rebex.Net.SshServerInfo
[03.01.2025 17:35:59.934] 31 (1) Establishing SSH Renci connection to host: 10.12.29.236...
[03.01.2025 17:35:59.939] 25 (1) Validating SSH public key...
[03.01.2025 17:35:59.939] 25 (1) Expected: AAAAC3NzaC1lZDI1NTE5AAAAIGIjodVxFRIcimmjOEDP5DNoTC7o1vWc8PWtxWFjLD+x
[03.01.2025 17:35:59.939] 25 (1) Received server key: AAAAC3NzaC1lZDI1NTE5AAAAIGIjodVxFRIcimmjOEDP5DNoTC7o1vWc8PWtxWFjLD+x
[03.01.2025 17:35:59.947] 31 (1) successfully connected
[03.01.2025 17:35:59.947] 31 (1) Created SSH connection implementation type: SshRenciConnectionImpl.
[03.01.2025 17:35:59.947] 31 (1) Executing: \echo $SHELL...
[03.01.2025 17:35:59.987] 31 (1) SSH output: /bin/bash
[03.01.2025 17:35:59.987] 31 (1) Opening shell: 22...
[03.01.2025 17:35:59.987] 31 (1) Establishing SSH Rebex connection to host: 10.12.29.236 (ID: 14772b77-072c-4849-9ee6-9420d08894b1)...
[03.01.2025 17:35:59.988] 31 (1) Warning: Failed to create Rebex (DSS/RSA) SSH connection. Switching to Renci SSH...
[03.01.2025 17:35:59.988] 31 (1) Warning: Negotiation failed. The client and the server have no common host key algorithm. Server supports 'rsa-sha2-512' which is not enabled at the client.
[03.01.2025 17:35:59.988] 31 (1) Type: Rebex.Net.SshException
[03.01.2025 17:35:59.988] 31 (1) Stack:
[03.01.2025 17:35:59.988] 31 (1) at Rebex.Net.Ssh.qvwcl(String p0, Int32 p1, SshParameters p2, zmezg p3)
[03.01.2025 17:35:59.988] 31 (1) at Veeam.SSH.Core.RebexSSHLib.SshRebexConnector.EstablishConnection(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator fingerprintChecker, Guid connectionId, SshRebexAuthenticator authenticator, String[] customHostKeyAlgorithms, ILogger logger, RebexSshClient& sshClient)
[03.01.2025 17:35:59.988] 31 (1) at Veeam.SSH.Core.RebexSSHLib.SshRebexConnectionImpl.<>c__DisplayClass14_0.<CreateEmulatingGranados>b__0(SshRebexConnectionImpl& impl)
[03.01.2025 17:35:59.988] 31 (1) at Veeam.Core.Memory.Disposable.Create[TValue](CreateAction`1 createInstance)
[03.01.2025 17:35:59.988] 31 (1) at Veeam.SSH.Core.SshConnection.CreateConnectionImpl(ISshConnectionConfig connSpec, ISshTargetHostFingerprintValidator sshTargetHostFingerprintValidator, ISshTransportEventsListener transportListener, ILogger logger)
[03.01.2025 17:35:59.988] 31 (1) SshStatus: OperationFailure
[03.01.2025 17:35:59.988] 31 (1) SshRemote: False
[03.01.2025 17:35:59.988] 31 (1) Status: OperationFailure
[03.01.2025 17:35:59.988] 31 (1) ProtocolCode: 0
[03.01.2025 17:35:59.988] 31 (1) ProtocolMessage: Unspecified
[03.01.2025 17:35:59.988] 31 (1) Warning: The client and the server have no common host key algorithm.
[03.01.2025 17:35:59.988] 31 (1) Type: Rebex.Net.SshException
[03.01.2025 17:35:59.988] 31 (1) Stack:
[03.01.2025 17:35:59.988] 31 (1) at ioqcn.shwed.scjzn(fblfl p0, SshKeyExchangeAlgorithm p1, SshHostKeyAlgorithm p2, pnrbh p3, pnrbh p4, ubycw p5, ubycw p6)
[03.01.2025 17:35:59.988] 31 (1) at Rebex.Net.SshSession.pfylg(Byte[] p0)
[03.01.2025 17:35:59.988] 31 (1) at Rebex.Net.SshSession.Negotiate()
[03.01.2025 17:35:59.988] 31 (1) at Rebex.Net.Ssh.tgdur.zsblg(zmezg p0, Boolean p1)
[03.01.2025 17:35:59.988] 31 (1) at Rebex.Net.Ssh.qvwcl(String p0, Int32 p1, SshParameters p2, zmezg p3)
[03.01.2025 17:35:59.988] 31 (1) SshStatus: OperationFailure
[03.01.2025 17:35:59.988] 31 (1) SshRemote: False
[03.01.2025 17:35:59.988] 31 (1) Status: OperationFailure
[03.01.2025 17:35:59.988] 31 (1) ProtocolCode: 3
[03.01.2025 17:35:59.988] 31 (1) ProtocolMessage: KeyExchangeFailed
[03.01.2025 17:35:59.988] 31 (1) SshServerInfo: Rebex.Net.SshServerInfo
[03.01.2025 17:35:59.988] 31 (1) Establishing SSH Renci connection to host: 10.12.29.236...
[03.01.2025 17:35:59.993] 86 (1) Validating SSH public key...
[03.01.2025 17:35:59.993] 86 (1) Expected: AAAAC3NzaC1lZDI1NTE5AAAAIGIjodVxFRIcimmjOEDP5DNoTC7o1vWc8PWtxWFjLD+x
[03.01.2025 17:35:59.993] 86 (1) Received server key: AAAAC3NzaC1lZDI1NTE5AAAAIGIjodVxFRIcimmjOEDP5DNoTC7o1vWc8PWtxWFjLD+x
[03.01.2025 17:36:00.002] 31 (1) successfully connected
[03.01.2025 17:36:00.002] 31 (1) Created SSH connection implementation type: SshRenciConnectionImpl.
[03.01.2025 17:36:00.056] 31 (1) Executing [22]: \export PS1="\[Veeam> \]"...
[03.01.2025 17:36:00.056] 86 (1) SSH output [22]: [?2004l
[03.01.2025 17:36:00.056] 31 (1) [?2004hVeeam>
[03.01.2025 17:36:00.056] 31 (1) Executing [22]: \stty -echo...
[03.01.2025 17:36:00.056] 86 (1) SSH output [22]: [?2004l
[03.01.2025 17:36:00.057] 31 (1) [?2004hVeeam>
[03.01.2025 17:36:00.057] 31 (1) Executing [22]: \bind 'set enable-bracketed-paste off'...
[03.01.2025 17:36:00.057] 86 (1) SSH output [22]: [?2004l
[03.01.2025 17:36:00.057] 31 (1) Veeam>
[03.01.2025 17:36:00.057] 31 (1) Executing [22]: echo test;...
[03.01.2025 17:36:00.058] 86 (1) SSH output [22]: test
[03.01.2025 17:36:00.058] 31 (1) Veeam>
[03.01.2025 17:36:00.058] 31 (1) Executing [22]: \unalias -a...
[03.01.2025 17:36:00.058] 31 (1) Veeam>
[03.01.2025 17:36:00.058] 31 (1) Executing [22]: locale -a | \grep en_US.utf8...
[03.01.2025 17:36:00.059] 86 (1) SSH output [22]: en_US.utf8
[03.01.2025 17:36:00.059] 31 (1) Veeam>
[03.01.2025 17:36:00.059] 31 (1) Executing [22]: export NLS_LANG=AMERICAN_AMERICA...
[03.01.2025 17:36:00.060] 31 (1) Veeam>
[03.01.2025 17:36:00.060] 31 (1) Executing [22]: echo $?...
[03.01.2025 17:36:00.060] 86 (1) SSH output [22]: 0
[03.01.2025 17:36:00.060] 31 (1) Veeam>
[03.01.2025 17:36:00.060] 31 (1) Executing [22]: export LC_ALL=en_US.UTF-8...
[03.01.2025 17:36:00.060] 31 (1) Veeam>
[03.01.2025 17:36:00.060] 31 (1) Executing [22]: echo $?...
[03.01.2025 17:36:00.060] 86 (1) SSH output [22]: 0
[03.01.2025 17:36:00.060] 31 (1) Veeam>
[03.01.2025 17:36:00.061] 31 (1) Checking elevation settings of account: proxy1... Elevate to root: False. Add to sudoers: False. Use su if sudo unavailable: False
[03.01.2025 17:36:00.061] 31 (1) Account elevation is not requested.
[03.01.2025 17:36:00.061] 31 (1) Closing shell: 22...
[03.01.2025 17:36:00.061] 31 (1) Disconnecting from: 10.12.29.236...
[03.01.2025 17:36:00.061] 31 (1) disconnected.
[03.01.2025 17:36:00.061] 31 (1) Disconnecting from: 10.12.29.236...
[03.01.2025 17:36:00.062] 31 (1) disconnected.
[03.01.2025 17:36:00.062] 31 (1) Warning: Failed to validate access to the server.
[03.01.2025 17:36:00.062] 31 (1) Warning: Elevation to root is required because the specified account does not have required privileges.
[03.01.2025 17:36:00.062] 31 (1) Type: System.Exception
[03.01.2025 17:36:00.062] 31 (1) Stack:
[03.01.2025 17:36:00.062] 31 (1) at Veeam.Core.Verify.That(Boolean condition, String message)
[03.01.2025 17:36:00.062] 31 (1) at Veeam.Linux.Client.Validators.LinuxServerAccessValidator.ValidateInternal(ILinuxConnectionConfig connectionConfig, Boolean isRootRequired, ISshTargetHostFingerprintValidator targetHostFingerprintValidator, ILogger logger, CancellationToken cancellationToken, Boolean& elevateToRootNotNeeded)
[03.01.2025 17:36:00.062] 31 (1) at Veeam.Linux.Client.Validators.LinuxServerAccessValidator.Validate(ILinuxConnectionConfig connectionConfig, ILogger logger, Boolean& elevateToRootNotNeeded, CancellationToken cancellationToken, Boolean isRootRequired, ISshTargetHostFingerprintValidator targetHostFingerprintValidator)
[03.01.2025 17:36:00.062] 31 (1) Warning: Cannot validate SSH credentials for server: 10.12.29.236
[03.01.2025 17:36:00.062] 31 (1) Warning: Failed to validate access to the Linux server: 10.12.29.236.
[03.01.2025 17:36:00.062] 31 (1) Type: System.Exception
[03.01.2025 17:36:00.062] 31 (1) Stack:
[03.01.2025 17:36:00.062] 31 (1) at Veeam.Linux.Client.Validators.LinuxServerAccessValidator.Validate(ILinuxConnectionConfig connectionConfig, ILogger logger, Boolean& elevateToRootNotNeeded, CancellationToken cancellationToken, Boolean isRootRequired, ISshTargetHostFingerprintValidator targetHostFingerprintValidator)
[03.01.2025 17:36:00.062] 31 (1) at Veeam.Archiver.Controller.Services.Sessions.ProxyServiceSession.<>c__DisplayClass31_0.<CheckLinuxProxyMachineCredentials>b__0()
[03.01.2025 17:36:00.062] 31 (1) at Veeam.Archiver.Controller.Services.Sessions.SshCredentialValidationResult.FromAction(String serverName, Action action)
[03.01.2025 17:36:00.062] 31 (1) Warning: Elevation to root is required because the specified account does not have required privileges.
[03.01.2025 17:36:00.062] 31 (1) Type: System.Exception
[03.01.2025 17:36:00.062] 31 (1) Stack:
[03.01.2025 17:36:00.062] 31 (1) at Veeam.Core.Verify.That(Boolean condition, String message)
[03.01.2025 17:36:00.062] 31 (1) at Veeam.Linux.Client.Validators.LinuxServerAccessValidator.ValidateInternal(ILinuxConnectionConfig connectionConfig, Boolean isRootRequired, ISshTargetHostFingerprintValidator targetHostFingerprintValidator, ILogger logger, CancellationToken cancellationToken, Boolean& elevateToRootNotNeeded)
[03.01.2025 17:36:00.062] 31 (1) at Veeam.Linux.Client.Validators.LinuxServerAccessValidator.Validate(ILinuxConnectionConfig connectionConfig, ILogger logger, Boolean& elevateToRootNotNeeded, CancellationToken cancellationToken, Boolean isRootRequired, ISshTargetHostFingerprintValidator targetHostFingerprintValidator)
-
- Service Provider
- Posts: 584
- Liked: 144 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
Re: v8 new installation - can not add linux proxy
24.04 is not supported
-
- Enthusiast
- Posts: 84
- Liked: 12 times
- Joined: Aug 21, 2018 5:33 am
- Contact:
Re: v8 new installation - can not add linux proxy
Thanks karsten123.
This time, I tried with ubuntu 22.04, and I get it to "work" =>
I was following my procedure to create a linux proxy for VBR => in this one, I wrote to check "Elevate specified account to root" and "Add account to the sudoers" and "Use su if sudo is unavailable"
Problem = for VBO proxy, we must uncheck "Add account to the sudoers" (this is already the case when using the only account created at installation time)
and we must uncheck "Use su if sudo is unavailable" because, with Ubuntu, this is sudo the right command
Otherwise, we got an error specifiying "Cannot find the server or the provided credentials are invalid"
But we still have to check the "Elevate specified account to root" (otherwise, we get the same error message)
Then we also have to do the "-dotnet" trick (blacklist)
and add the nano package to edit the hosts file :
and edit the linux host file
=> add the IP and name of the windows veeam server (CTRL+O to save, CTRL+X to close nano)
=> I also had to disable the Veeam Windows server firewall for the connection to be successful (when adding new linux proxy, and also when adding new repo and trying to set the proxy)
This time, I tried with ubuntu 22.04, and I get it to "work" =>
I was following my procedure to create a linux proxy for VBR => in this one, I wrote to check "Elevate specified account to root" and "Add account to the sudoers" and "Use su if sudo is unavailable"
Problem = for VBO proxy, we must uncheck "Add account to the sudoers" (this is already the case when using the only account created at installation time)
and we must uncheck "Use su if sudo is unavailable" because, with Ubuntu, this is sudo the right command
Otherwise, we got an error specifiying "Cannot find the server or the provided credentials are invalid"
But we still have to check the "Elevate specified account to root" (otherwise, we get the same error message)
Then we also have to do the "-dotnet" trick (blacklist)
and add the nano package to edit the hosts file :
Code: Select all
sudo apt-get install nano
Code: Select all
sudo nano /etc/hosts
=> I also had to disable the Veeam Windows server firewall for the connection to be successful (when adding new linux proxy, and also when adding new repo and trying to set the proxy)
-
- Enthusiast
- Posts: 84
- Liked: 12 times
- Joined: Aug 21, 2018 5:33 am
- Contact:
Re: v8 new installation - can not add linux proxy
new problem = I have to keep the windows firewall stopped, otherwise, I can't run a VBO job = after sarting a job, I get a dialog box saying "Job was unable to start within the configured timeout"
-
- Influencer
- Posts: 18
- Liked: 1 time
- Joined: Oct 22, 2018 8:31 am
- Full Name: Michael Schwarzer
- Contact:
Re: v8 new installation - can not add linux proxy
Hello sogapex&ronnypot,
run through the same situation. The log is showing the the key exchange for the ssh session was not successfull. may be tuning the ssh client configuration at the new proxy and adding:
points you in the right direction
run through the same situation. The log is showing the the key exchange for the ssh session was not successfull. may be tuning the ssh client configuration at the new proxy and adding:
Code: Select all
HostKeyAlgorithms=+ssh-sha2-512
PublickeyAcceptedAlgorithms=+ssh-sha2-512
-
- Enthusiast
- Posts: 84
- Liked: 12 times
- Joined: Aug 21, 2018 5:33 am
- Contact:
Re: v8 new installation - can not add linux proxy
Hi, since then : firewall disabled = everything works great
As soon as I activate it : the job is stuck (can't communicate with the proxy) => no way to abort it
So, finally, I manually added a specific "inbound rule" in the windows server firewall :
Protocol Type => TCP
Scope => local IP = any / remote IP = linux proxy IP
And the job "unstucks" by itself almost immediately
regards
As soon as I activate it : the job is stuck (can't communicate with the proxy) => no way to abort it
So, finally, I manually added a specific "inbound rule" in the windows server firewall :
Protocol Type => TCP
Scope => local IP = any / remote IP = linux proxy IP
And the job "unstucks" by itself almost immediately
regards
-
- Novice
- Posts: 7
- Liked: 3 times
- Joined: Dec 18, 2024 1:24 pm
- Full Name: Ronny Pot
- Contact:
Re: v8 new installation - can not add linux proxy
Hi,
We had the same issue and created a manual firewall rule by allowing the TCP ports: 4222, 5432, 9191, 9193 and 9194.
All listed in this document: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=80
We had the same issue and created a manual firewall rule by allowing the TCP ports: 4222, 5432, 9191, 9193 and 9194.
All listed in this document: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=80
-
- Service Provider
- Posts: 21
- Liked: 5 times
- Joined: Feb 22, 2024 1:37 pm
- Contact:
Re: v8 new installation - can not add linux proxy
Worked for me today, thanksflavio.santos wrote: ↑Sep 04, 2024 3:23 am We can solve this one, the problem was solved by the HOSTS file. Proxy talk with the VBO server using the server name, not the IP.
My bad.

-
- Service Provider
- Posts: 56
- Liked: 23 times
- Joined: Mar 28, 2020 3:50 pm
- Full Name: Greg Tellone - Cloud IBR
- Contact:
Re: v8 new installation - can not add linux proxy
Having a similar issue when adding a linux proxy. The ui displays:
"Configure proxy. Error: Failed to perform endpoint handshake. :: 0:00:40"
Logs show some of the same errors as previously written about:
Confirmed firewall is not blocking traffic and DNS resolution is working.
Running the latest VBO 8.1.0.3503. Tried with brand new installs of Ubuntu 22.04 and 24.04 (which is now supported) but get same error.
Also upgraded VBO Server OS from 2019 to 2022 but no change.
Veeam support tech from ticket 07622185 had me add "HostKeyAlgorithms +ssh-rsa,rsa-sha2-512" to the /etc/ssh/sshd_config and restart ssh but that didn't fix the issue.
Is it possible that the Windows OS isn't configured to support that host key algorithm? Haven't been able to find any useful information on how to add that to the Window servers. Any other ideas? Thanks!
"Configure proxy. Error: Failed to perform endpoint handshake. :: 0:00:40"
Logs show some of the same errors as previously written about:
Code: Select all
[06.03.2025 14:31:01.409] 50 (1) Establishing SSH Rebex connection to host: vboproxy50 (ID: 120435d7-7a3b-4da3-afdd-9b38c8f230ec)...
[06.03.2025 14:31:01.415] 50 (1) Warning: Failed to create Rebex (DSS/RSA) SSH connection. Switching to Renci SSH...
[06.03.2025 14:31:01.415] 50 (1) Warning: Negotiation failed. The client and the server have no common host key algorithm. Server supports 'rsa-sha2-512' which is not enabled at the client.
Running the latest VBO 8.1.0.3503. Tried with brand new installs of Ubuntu 22.04 and 24.04 (which is now supported) but get same error.
Also upgraded VBO Server OS from 2019 to 2022 but no change.
Veeam support tech from ticket 07622185 had me add "HostKeyAlgorithms +ssh-rsa,rsa-sha2-512" to the /etc/ssh/sshd_config and restart ssh but that didn't fix the issue.
Is it possible that the Windows OS isn't configured to support that host key algorithm? Haven't been able to find any useful information on how to add that to the Window servers. Any other ideas? Thanks!
-
- Service Provider
- Posts: 56
- Liked: 23 times
- Joined: Mar 28, 2020 3:50 pm
- Full Name: Greg Tellone - Cloud IBR
- Contact:
Re: v8 new installation - can not add linux proxy
Did a webex screenshare with support today and the issue is being escalated to L2. Will update this post with resolution once found. Thank you!
-
- Service Provider
- Posts: 42
- Liked: 5 times
- Joined: Oct 17, 2016 1:03 am
- Contact:
Re: v8 new installation - can not add linux proxy
I ran into the same thing - Running the latest VBO 8.1.0.3503 on Win2022. Brand new install of Ubuntu 24.04 with error specifiying "Cannot find the server or the provided credentials are invalid" Seems to be the same as sogapex. DNS is configured and resolves both from Windows and Ubuntu, tested without any Windows/Ubuntu firewalls active. SSH from the latest Putty install from the Windows VBO server works without issue.
-
- Service Provider
- Posts: 56
- Liked: 23 times
- Joined: Mar 28, 2020 3:50 pm
- Full Name: Greg Tellone - Cloud IBR
- Contact:
Re: v8 new installation - can not add linux proxy
Upgraded to 8.1.1.159 today but that didn't help either.
-
- Novice
- Posts: 3
- Liked: never
- Joined: May 08, 2018 7:34 am
- Full Name: Peter Steffan
- Contact:
Re: v8 new installation - can not add linux proxy
We have exactly the same issue.
- VBO: 8.1.1.159 on Windows Server 2022
- Proxy: Ubuntu 24.04
When we try to add a linux proxy, we get following errors:
[Warning] Warning: Failed to create Rebex (DSS/RSA) SSH connection. Switching to Renci SSH...
[Warning] Warning: Negotiation failed. The client and the server have no common host key algorithm. Server supports 'rsa-sha2-512' which is not enabled at the client.
[Warning] SshStatus: OperationFailure
[Warning] SshRemote: False
[Warning] Status: OperationFailure
[Warning] ProtocolCode: 0
[Warning] ProtocolMessage: Unspecified
[Warning] Warning: The client and the server have no common host key algorithm.
[Warning] SshStatus: OperationFailure
[Warning] SshRemote: False
[Warning] Status: OperationFailure
[Warning] ProtocolCode: 3
[Warning] ProtocolMessage: KeyExchangeFailed
[Warning] SshServerInfo: Rebex.Net.SshServerInfo
We tried:
- SSH /etc/ssh/sshd_config customization --> after that no ssh connection was possible, so reverse
- DNS check (forward and reverse is possible)
- Same time and date on all servers
- Firewall disabled
Has anyone a solution for that from veeam support?
- VBO: 8.1.1.159 on Windows Server 2022
- Proxy: Ubuntu 24.04
When we try to add a linux proxy, we get following errors:
[Warning] Warning: Failed to create Rebex (DSS/RSA) SSH connection. Switching to Renci SSH...
[Warning] Warning: Negotiation failed. The client and the server have no common host key algorithm. Server supports 'rsa-sha2-512' which is not enabled at the client.
[Warning] SshStatus: OperationFailure
[Warning] SshRemote: False
[Warning] Status: OperationFailure
[Warning] ProtocolCode: 0
[Warning] ProtocolMessage: Unspecified
[Warning] Warning: The client and the server have no common host key algorithm.
[Warning] SshStatus: OperationFailure
[Warning] SshRemote: False
[Warning] Status: OperationFailure
[Warning] ProtocolCode: 3
[Warning] ProtocolMessage: KeyExchangeFailed
[Warning] SshServerInfo: Rebex.Net.SshServerInfo
We tried:
- SSH /etc/ssh/sshd_config customization --> after that no ssh connection was possible, so reverse
- DNS check (forward and reverse is possible)
- Same time and date on all servers
- Firewall disabled
Has anyone a solution for that from veeam support?
Peter Steffan - My Blog: petersvirtualworld.de; VMCE2024, VMCA2024, Vanguard
-
- Service Provider
- Posts: 56
- Liked: 23 times
- Joined: Mar 28, 2020 3:50 pm
- Full Name: Greg Tellone - Cloud IBR
- Contact:
Re: v8 new installation - can not add linux proxy
No luck yet. Our case # 07622185 is still being investigated. Will ask for it to be escalated again.
And the same proxy can be added to a different VBO server successfully, so doesn't seem like an issue with the Ubuntu server.
And the same proxy can be added to a different VBO server successfully, so doesn't seem like an issue with the Ubuntu server.
-
- Novice
- Posts: 3
- Liked: never
- Joined: May 08, 2018 7:34 am
- Full Name: Peter Steffan
- Contact:
Re: v8 new installation - can not add linux proxy
We fixed it for our environment.
- enabled firewall again
- edited hosts file on Proxies and added: VBO and other Proxies --> reboot
after editing hosts file the adding proxy wizard was successfull
I don't know exactly where the problem comes from, but I have the assumption that SSH or the key issue does not use the classic DNS resolving, but instead needs the hosts file.
- enabled firewall again
- edited hosts file on Proxies and added: VBO and other Proxies --> reboot
after editing hosts file the adding proxy wizard was successfull
I don't know exactly where the problem comes from, but I have the assumption that SSH or the key issue does not use the classic DNS resolving, but instead needs the hosts file.
Peter Steffan - My Blog: petersvirtualworld.de; VMCE2024, VMCA2024, Vanguard
-
- Service Provider
- Posts: 56
- Liked: 23 times
- Joined: Mar 28, 2020 3:50 pm
- Full Name: Greg Tellone - Cloud IBR
- Contact:
Re: v8 new installation - can not add linux proxy
Just tried adding the VBO's and proxies to /etc/hosts and reboot again and didn't help in our case. Added both short name and fqdn for all the hosts:
x.x.x.x servername servername.sampledomain.com
x.x.x.x servername servername.sampledomain.com
Who is online
Users browsing this forum: No registered users and 325 guests