This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
The first thing I'd suggest would be to make sure that your Alteryx Server is setup to be able to handle Insights. You might be running into an issue where Insights are disabled on your server if you have not gone through the Alteryx System Settings since upgrading your server.
If you've already done this, make sure your workflow was also uploaded to the Gallery, as is noted in the documentation here:
@aguisande Can you advise if your Gallery base URL is http(s)://hostname/gallery/ or http(s)://hostname/? If your Gallery does not use the '/gallery' path can you try adding it back to see if it resolves your issue?
@aguisande Thank for confirming. If you have followed all of @MikeSp's recommendations (please double check this), your gallery is using the http(s)://hostname/gallery url, and you are still encountering this error I would recommend opening a case with support. This way we can schedule a some time to take a look at this with you. Please include a link to this post in your support request.
I actually chatted with @JakeS while you were encountering this issue. I believe yours might've had to do with the "-" at the beginning of your machine's hostname and I'm not sure it would've been specifically related to the license. However, with the licensing the license is tied to the machine's hostname which is likely why you had to re-license.
The thought from the support side at the moment is the Insight rendering may have been trying to use something like "http://-hostname-1" where a dash at the beginning of the URL seems to have been confusing the Insight worker and throwing a bad host error in the service logs.
As an interesting read, RFC942 mentions that hostnames ideally not begin with a non-alpha character for internet operations (see assumptions section, point 1). This may be why we were encountering the issue.