Monaco 2.0 - URL mismatch during direct download
GarrettHaines opened this issue · 4 comments
I am attempting a direct download on Monaco 2.0 using "monaco download direct [URL] [token]" but am getting this issue:
As you can see, a request is being made to "URL/api/v1/config/..." as I have highlighted. However, it appears the config API for our tenant is formatted as "URL/api/config/v1/..." as shown below:
Is this a bug? Could it have anything to do with the fact that I am using a managed deployment? I need to transfer our managed tenant configs/settings over to a SaaS-based tenant as painlessly as possible, if possible. We have hundreds of management zones, application detection rules, and more that need to be transferred.
Thank you!
Hi @GarrettHaines,
the API that is being called in this specific case is the Environment API v1.
It has a /config/clusterversion endpoint, thus the confusing /api/v1/config/...
The issue seems to be that the hostname of your managed environment can't be resolved.
Can you ping it from the same machine? I'd assume you see the same issue there.
You can either check the DNS configuration or hosts entry, or if you know it try configuring the IP address directly in the manifest, instead of the hostname.
Hello @UnseenWizzard,
Did you notice the difference in the path that I mentioned? A request is being made to "/api/v1/config/..." but shouldn't it be "/api/config/v1/..." as shown in the screenshot? I have not configured a manifest, as I am trying to download the configurations directly.
Hi @GarrettHaines,
I did notice that. I hope you noticed the API it is trying to query, as I pointed out in my reply above:
the API that is being called in this specific case is the Environment API v1 (/api/v1).
It has a /config/clusterversion endpoint, thus the confusing /api/v1/config/...
What I said above about verifying that the machine can actually resolve the host or trying the IP instead applies to direct downloads as well of course.
If you try the IP instead of hostname you'd just have to pass it as the URL argument rather than write it into the manifest of course.
The issue seems to be that the hostname of your managed environment can't be resolved.
Can you ping it from the same machine? I'd assume you see the same issue there.
The relevant part in the error output is:
dial TCP: lookup {your host}: no such host
Thank you! Was not on client's network.