cnmaestro on-premises discovery failed epmp v3.5.1

[someone]

Hi people, is anyone else experiencing issues with cnmaestro onboarding on version 3.5.1?

I get failed message:

Sep  1 21:01:11 User DEVICE-AGENT[4211]: getaddrinfo failed with error_code=-2
Sep  1 21:01:11 User DEVICE-AGENT[4211]: Not able to resolve <cnmaestro.URL>
Sep  1 21:01:11 User DEVICE-AGENT[4211]: Not able to resolve  <cnmaestro.URL> 
Sep  1 21:01:11 User DEVICE-AGENT[4211]: OpenConnection to <cnmaestro.URL>:443 failed 
Sep  1 21:01:11 User DEVICE-AGENT[4211]: Unable to discover cnMaestro URL (re-discover in 347 seconds)
Sep  1 21:01:11 User DEVICE-AGENT[4211]: Attempting (re)connection in 5 minutes

In this log I replaced our cnmaestro url to <cnmaestro.URL> for obvious reasons.

Before you ask, yes the cnmaestro.URL is reachable by the CPE so DNS is working and I can ping the URL.

If I change the url from "cnmaestro.URL" to "https://cnmaestro.URL " then it onboards without error.

The strange thing is if I update an older version that was already onboarded to 3.5.1 then it happens that sometime it cannot connect anymore to cnmaestro until I replace "https://cnmaestro.URL" to "cnmaestro.URL", so what is the issue here and why is this happening?

[Jordan]

In the second scenario for already onboarded device, does the device connect if you disable Remote Mangement, save, enabled Remote Management and then save without changing the URL?  It might just be triggering a reconnection attempt when you add/remove https:// to the URL.

[Cambium_Rupam]

In the older version of ePMP below 3.5.1 adding "https://cnmaestro.URL" was mandatory.

But from 3.5.1 onwards device should work with  "cnmaestro.URL" (specifying https:// is not mandatory)

We dont see any issue with our devices running 3.5.1 with or without https:// in front of the cnmaestro URL.

Rupam