Jekyll-algolia Plugin Error "Not enough rights to add an object"

[wangzhukang]

Hello everyone, I encountered an issue when using the Jekyll-algolia plugin to build the index, and I hope someone can help me resolve it.

Problem Description

When running the following command:

bundle exec jekyll algolia

I received the following error:

[jekyll-algolia] Error: 400: Cannot POST to https://CS6SCKSE72.algolia.net/1/indexes/*/batch: {"message":"Not enough rights to add an object near line:1 column:3718","status":400} (400) 

Environment Information

Here are the details of my project environment:

• wsl2-ubuntu (24.04)
• ruby (3.2.0)
• gem (3.4.1)
• bundler (2.5.23)
• jekyll (3.10.0)
• jekyll-algolia (1.7.1)

Gemfile Configuration

Below is the content of my Gemfile:

source "https://rubygems.org"

gem "github-pages", group: :jekyll_plugins
gem "jekyll-include-cache", group: :jekyll_plugins

group :jekyll_plugins do
    gem "jekyll-feed"
    gem "jekyll-seo-tag"
    gem "jekyll-sitemap"
    gem "jekyll-paginate"
    gem "jekyll-algolia"
end

I have already run bundle install and bundle update, and no errors occurred during these steps.

Plugin Configuration

My Jekyll-algolia settings in _config.yml are as follows:

algolia:
  application_id         : CS6SCKSE72
  index_name             : wangzhukangio
  search_only_api_key    : 8358033c91630aa122127adfee9bd4d6
  powered_by             : true # true (default), false
  files_to_exclude:
    - _pages/404.md

I have also added the admin API key (in fact I can only find write API Key as a private API key in my algolia dashboard which I treat as my admin API key, I'm not sure if there's a problem here) to the environment variables.

Actions Attempted

I created a test page in _pages/index.md and attempted to build the index using bundle exec jekyll algolia, but the error mentioned above occurred.

Source Code

The code for my project can be found at this repo, and the pages currently hosted by GitHub Pages can be accessed at this website. The search function powered by algolia is currently enabled, but nothing can be searched.

Question

• What might be causing this issue?
• Could it be related to API permissions, index configuration, or plugin version?
• What are the recommended steps to troubleshoot or resolve this problem?

Thank you very much for any help, please let me know if more information is needed.

[wangzhukang]

Well, I have found the problem. Because I applied for the Algolia DocSearch plan and DocSearch doesn't provide the admin API key. I have now re-applied for the Algolia Build plan and have resolved the issue.