I don't think I have access to the right Algolia projects, but we just need to set the app ID that was removed in this commit: 1bd4b25

cc: @markerikson

Yeah, the Algolia setup has been broken or weird for the last year or so.

We've got 2-3 different projects in Algolia. There was an old-style key for an old project and some kind of upgrade/migration step that didn't get done by their deadline. I thought I fixed it with a new key after talking to support, but maybe that didn't work right?

Hey guys,

Looks like the appId is still required for the current setup. With the current config appId: ' ', requests fail because the appId is used in the URL generation https://{APPLICATION_ID}.algolia.net.

When I reverted the value for appId based on 1bd4b25, I no longer got the DNS error above. However, there is new 400 error:

{
  "message": "indexName is not valid",
  "status": 400
}

Based on this support article, this error occurs in two cases:

1. indexName does not match the indexName issued in your DocSearch acceptance email
2. incorrect API key is used

Then I tried to fetch all indecies via GET https://g15kg9hemq.algolia.net/1/indexes?x-algolia-api-key=2d058d216b7fd5d68d481fd48ee72c06&x-algolia-application-id=G15KG9HEMQ which resulted in 403 error below:

{"message":"Invalid Application-ID or API key","status":403}

Looks like the App ID & API key are no longer valid.