Veeam Cloud Connect "Connection to Cloud Provider cannot be established"

Hi @Mykah , are you trying to add the SP for the VBR console of a tenant, right?

Have you checked if the VBR server is able to solve with DNS and telnet the cloud gateway port (default is 6180)?

Whats versions are both tenant and SP VBR server?

hi @marco_s ,
both of the installations are on version 12.1.
And yes im trying to connect as a Tenant on our SP console for VBR.

Net-TestConnection on our “URL” via 6180 works fine.

Ok..have you also verified if tenant’s server is able to access the CRL website?

@marco_s u mean from the provider of the Certificate?
sorry for askin but im kinda new into that stuff.

No problem..yes, I mean, CA who issue the SP certificate.

Anyway, you can try to search other info in the log, typically under C:\ProgramData\Veeam\Backup\CloudConnectService

https://www.veeam.com/kb2096

EDIT: added official KB for logs

[26.02.2024 08:17:31.581]   <195>    Info (3)    [VccAuthenticate] Authentication as the tenant Test
[26.02.2024 08:17:36.201]   <195>   Error (1)    [VccSocketInvokerDispatcher]  Failed to establish new connection from [::ffff:x.x.x.x]:60673
[26.02.2024 08:17:36.201]   <195>   Error (1)    Über das Ende des Datenstroms hinaus kann nicht gelesen werden. (System.IO.EndOfStreamException)
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei System.IO.__Error.EndOfFile()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei System.IO.BinaryReader.FillBuffer(Int32 numBytes)
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei System.IO.BinaryReader.ReadInt32()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.Transport.CMessageReader.ReadMessageSafe[T]()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.Transport.CMessageReader.ReadMessage[T]()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.Transport.CMessageReaderLoggingDecorator.ReadMessage[T]()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.Transport.CVccPersistentConnectionInitializationIo.ReadGateways()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.Transport.CVccPersistentConnectionInitializationPipelineV12.InitializeServer(IVccPersistentConnectionServerInitializationContext context)
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.ServerTransport.CVccServerTransportConnectionInitializer.Initialize(IServerTransportConnection transportConnection)
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.ServerTransport.CVccServerTransportConnectionEstablisher.EstablishNewConnection(TcpClient client)
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.ServerTransport.CSocketInvokerAcceptedConnectionDispatcher.HandleSocketSafe(Socket socket)

Thats what i found in the logs on the SP Server
Also @Chris.Childerhose, i get a certificate warning that mentioned that the certificate is untrusted or self-signed.

Mmm, ok..what about logs under %ProgramData%\Veeam\Backup\Svc.VeeamGateSvc* of your Cloud Gateways ?

i guess i found the problem:

failed to resolve host name or IP address cgw2.placeholder.de from placeholder-server
Unable to obtain IP addresses for host 'cgw1placeholder.de'

can it be?

Yes, it could be..is the CC environment new?

Anyway, verify your cloud gateways settings, and DNS resolution as well

https://helpcenter.veeam.com/docs/backup/cloud/cloud_connect_gateway_settings.html?ver=120

EDIT:  @Mykah in addition, it seems your gateways have the same public ip..

Hello,
so i fixed the communication between the CloudGateways and also i can validate the Certificate from the CA.
Im still not able to connect my Test-Tenant to the SP.
Still getting this ERROR:
26.02.2024 08:17:31.581]   <195>    Info (3)    [VccAuthenticate] Authentication as the tenant Test
[26.02.2024 08:17:36.201]   <195>   Error (1)    [VccSocketInvokerDispatcher]  Failed to establish new connection from [::ffff:x.x.x.x]:(DYNAMIC PORT)
[26.02.2024 08:17:36.201]   <195>   Error (1)    Über das Ende des Datenstroms hinaus kann nicht gelesen werden. (System.IO.EndOfStreamException)
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei System.IO.__Error.EndOfFile()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei System.IO.BinaryReader.FillBuffer(Int32 numBytes)
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei System.IO.BinaryReader.ReadInt32()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.Transport.CMessageReader.ReadMessageSafe[T]()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.Transport.CMessageReader.ReadMessage[T]()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.Transport.CMessageReaderLoggingDecorator.ReadMessage[T]()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.Transport.CVccPersistentConnectionInitializationIo.ReadGateways()
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.Transport.CVccPersistentConnectionInitializationPipelineV12.InitializeServer(IVccPersistentConnectionServerInitializationContext context)
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.ServerTransport.CVccServerTransportConnectionInitializer.Initialize(IServerTransportConnection transportConnection)
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.ServerTransport.CVccServerTransportConnectionEstablisher.EstablishNewConnection(TcpClient client)
[26.02.2024 08:17:36.201]   <195>   Error (1)       bei Veeam.Backup.CloudConnect.ServerTransport.CSocketInvokerAcceptedConnectionDispatcher.HandleSocketSafe(Socket socket)
 

Are you using port 6180 for the connection?  That is the default port for VCC.

Yes i do. :/

Ok.  You might require a support case at this point to determine the issue as it is hard from that log snippet above to know what is causing the issue.

Hello Guys,

i found the solution for the problem, i had to configure the “hosts” file from Windows. First i put for the IPs the URL in the Certificate, that was the Problem. I had to enter the CloudGateway DNS Name configured in Veeam on the SP site.

So DNS was the issue here.

Thanks for help Guys!

Great to hear you addressed the issue. It is always DNS. 😜😂

Hi all!

I do have the same problem, but unfortunately is not a DNS issue, so the above discussion didn'’t help me.

When I am trying to connect a customer’s server on the provider’s server via “Cloud Connect”, I am getting the following error in the log file “C:\ProgramData\Veeam\Backup\CloudConnectService\Svc.VeeamCloudConnect.log”:

[04.04.2025 14:58:07.492]    <70>   Error (1)    [VccSocketInvokerDispatcher]  Failed to establish new connection from [2a11:xxxx::xxxx]:random-port
[04.04.2025 14:58:07.492]    <70>   Error (1)    The credentials supplied to the package were not recognized (System.ComponentModel.Win32Exception)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at System.Net.Security.SecureChannel.AcquireServerCredentials(Byte[]& thumbPrint)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at Veeam.Backup.CloudConnect.ServerTransport.CTcpServerTransportConnection.Start(X509Certificate2 certificate, SslProtocols enabledSslProtocols)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at Veeam.Backup.CloudConnect.ServerTransport.CTcpServerTransportConnection..ctor(TcpClient client, X509Certificate2 certificate, IAllowedPackageSizeProvider allowedPackageSize, ILimitedCompressionService compressionService, IVccTransportServerSideOptions options, IScopedLogger log)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at Veeam.Backup.CloudConnect.ServerTransport.ServerTransportConnectionFactory.Create(TcpClient tcpClient, IAllowedPackageSizeProvider allowedPackageSize)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at Veeam.Backup.CloudConnect.ServerTransport.CVccServerTransportConnectionEstablisher.EstablishNewConnection(TcpClient client)
[04.04.2025 14:58:07.492]    <70>   Error (1)       at Veeam.Backup.CloudConnect.ServerTransport.CSocketInvokerAcceptedConnectionDispatcher.HandleSocketSafe(Socket socket)
 

And on the customer’s server I am getting the following message:

Certificate validation failed. Authentication failed because the remote party has closed the transport stream.

Certificate: Unknown

Any ideas what could bring this problem?

Thanks a lot in advance for your prompt attention to this matter and for your support!

With kind regards,

Angelos Pitsos

Hi there!

Finally I managed to solve the problem. I opened a ticket and a Veeam technician checked the logs and he told me that the problem was purely with SSL. He suggested me to reissue the SSL certificate and re-install it. That actually solved the problem.

Thanks a lot anyway, even for reading my post. Wishing you all a nice weekend!

With kind regards,

Angelos Pitsos