Hi all,

we've run into an issue after installing an on-prem DMA with STaaS enabled.
The installation appeared to complete successfully, and DataMiner starts up, but after a few minutes it shuts itself down again.

The exception in CloudStorage.txt looks like this:

2026/07/20 16:06:29.652|SLLog|ApplyLogLevels|CRU|-1|Log Levels: Info: 0; Error: 0; Debug: 0 (from LogSettings.xml)
2026/07/20 16:06:29.662|SLDataGateway|DataGateway.CloudStorage.ConnectionComposing|INF|0|1|Composing cloud storage connection.
2026/07/20 16:06:29.665|SLDataGateway|DataGateway.CloudStorage|INF|0|1|Start initialization CloudStorageManager...
2026/07/20 16:06:29.668|SLDataGateway|DataGateway.CloudStorage|INF|0|1|Creating services...
2026/07/20 16:06:29.733|SLDataGateway|DataGateway.CloudStorage|INF|0|1|Creating CloudStorageConnection services...
2026/07/20 16:06:29.748|SLDataGateway|DataGateway.CloudStorage|INF|0|1|Getting CloudSettings from repository...
2026/07/20 16:06:51.111|SLDataGateway|DataGateway.CloudStorage|INF|0|61|Retrying request due to exception.
Azure.RequestFailedException: An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 20.31.240.20:443
at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Azure.Core.Pipeline.HttpClientTransport.<ProcessSyncOrAsync>d__11.MoveNext()
--- End of inner exception stack trace ---
at Azure.Core.Pipeline.HttpClientTransport.<ProcessSyncOrAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Azure.Core.Pipeline.HttpPipelineTransportPolicy.<ProcessAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Azure.Core.Pipeline.ResponseBodyPolicy.<ProcessAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Azure.Core.Pipeline.RedirectPolicy.<ProcessAsync>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Azure.Core.Pipeline.RetryPolicy.<ProcessAsync>d__5.MoveNext()

From what we can see, the DMA is unable to reach 20.31.240.20:443, even though all required prerequisites should be in place.
The installation itself completed cleanly after we resolved a proxy-related issue (see Registering on-prem DMA with dataminer.services/STaaS via proxy fails - DataMiner Dojo).

As far as we know, we've covered all requirements for an on-prem DMA with STaaS, including access to the required dataminer.services endpoints/IP addresses and other documented requirements such as

• <DataBase .... type="CloudStorage"/> in Db.xml
• <HTTPS enabled="true" name="10.20.30.40" /> in MaintenanceSettings.xml

We're also struggling a bit with troubleshooting because many of the available guides assume that the DMA is running and that Cube can be used. Since the DMA shuts down shortly after startup, those approaches don't really help us.

Has anyone seen something similar before or has any ideas on what else we could check? It's entirely possible that we've overlooked something, so we're open to any suggestions.

Thanks,

Jörg