401 API Key Not Supplied Unless in Header

🚀 Support (Q&A)
1

Hi there, we are running into an issue when deploying to Azure IIS following the guide Rhino - Deployment to Production Servers - the VM is up and running, and attached are screenshots showing that when making the request with RhinoComputeKey and our API key alone we get a 401 error with the message “API Key Not Provided” but when we make the request using insomnia to add our API Key directly to the header, we get a 200 response with “compute.rhino3d” as the output - even trying to use a Hops element in Grasshopper says “Cannot communicate with the server” - is there any way to force the grasshopper worker to add our API key to the headers of the request?

Thanks

200 Header
200 Header1919Ă—1079 149 KB

401 Pack
401 Pack1919Ă—1079 159 KB

2

Hi Joshua,

Currently, the GrasshopperWorker does not include sending an API Key, as it expects the RhinoCompute instance to run on a Local Machine (not something that is accessible to the internet and requires authentication, like this IIS implementation).

We do have some documentation on how to set this up using a Rhino Compute Server hosted on a server: Connect your app to a Rhino Compute Server.

Please let me know if this helps!