Hi, I have a grist self-hosted instance running on my own domain (grist.mydomain.com) and not the hosted docs.getgrist.com domain.
I am trying to add a connection to the grist API.
When I enter my URL as the domain and my API key as required and click save, I get a 401 error, but no other information.
The API endpoint works OK and gives a valid response when I curl to it:
curl -H “Authorization: Bearer ” https://grist.mydomain.com/api/orgs/
Any idea why the grist connector doesn’t work on my custom domain?
Thanks, Matt.
Hello @Matthew_Grant and welcome to the Make Community!
So just to be sure, you’re entering the domain as grist.mydomain.com?
Not including any https:// or any trailing forward slash?
Are you self-hosting on your premises or in the cloud?
I ask for clarification because when you run cURL that’s a local connection to your locally-hosted system, but running from Make goes over Internet and gets all kinds of more complicated, as I’m sure you can imagine.
Hi Donald,
yes, just the grist.mydomain.com no https or trailing slash, and just the API key in the key field.
I am self-hosting behind an nginx proxy manager which forwards grist.mydomain.com to localhost:8484
I got excited when you mentioned the local curl, and thought we might have solved it, but I have since tried the curl when connected to a different ISP (outside my local network) and the curl gives a valid response from there also. I can also login to grist remotely and see/edit my docs, so the connection all seems good.
Could there be something else that the Make connector is doing in the background that’s more complex than a simple curl?
Something else that needs to be forwarded?
Make modules have a URL they hit when you attempt to set up a connection. As far as I know, there’s no way to know what that URL is without asking Make or the developer.
You can try setting up your own custom API connection using HTTP module to at least prove you can connect from Make.
Then once you’ve gathered that extra bit of info, open a ticket with the Make team about it.
Thanks Donald,
That’s worked a treat!
The HTTP module successfully connects to the API with only the grist.mydomain.com URL and header Authorization= Bearer , so it must be something internal to the Grist connector that’s blocking it.
I’ll log a ticket.
2 Likes