Hi Dojo,
For an internal Skyline setup I have created a new self-hosted-agent and made it cloud connected.
At first all seems running fine (running on current latest feature release 10.4.1).
My APPS are available over the cloud features, but I'm having trouble with the remote Cube access.
The client I'm trying to connect is inside the same HQ network, so I was expecting this to work without any issues.
When connecting to the cube, I see following error:
While surely the agent is running fine.
When changing the connection setting from "AUTO" to "gRPC", it remains stuck on "Connecting... Logging on..."
What logs can I check? or how can I move forward please? Thanks!
even though the endpoints show in cube the green flag “HTTPS available”. I did noticed now that the maintenanceSettings.xml didn’t contain the HTTPS tag at all.
After adding this TAG and restarting DataMiner, the whole cloud remote pages seemed to be offline (404 error). So also the monitoring app and dashboards were no longer reachable.
I now selected in IIS site bindings a different SSL certificate (issued by the network, instead of the selected one “Auto-created Cert by APIGateway”.
And after a refresh, I now seem to have all my cloud features working, including the remote cube.
Do please share if these actions sound correct, or if I have to revert certain steps. Thanks!
Hi Thijs
For Remote Cube we indeed require HTTPS to be configured (with a valid certificate). This is noted in the list of requirements on the internal docs page. I'll follow up to move these requirements also to the public docs as Remote Cube was made available for users as well.
Wkr
Thanks Jordy, The strange thing is that in cube the green flag showed “HTTPS available”, (because the ports were already open), but the DataMiner itself didn’t had the HTTPS tag properly configured. After this configuration, and the selection of the correct certificate in IIS, everything worked out. Thanks for the confirmation on this!
Yes, I suspect Cube is only seeing the HTTPS from .on.dataminer.services which is working fine, but the actual connection on the DataMiner server itself wasn’t.
the endpoint I tried with is: “https://[dms_name]-[company_name].on.dataminer.services”
as well as “https://[cloudAgent_GUID].on.dataminer.services”