Error at login & in logs for netlify plugin search

I get the following login error when I build my website using netlify and eleventy.

  • Internal Error: Got status code 500
    from /api/netlify/me
    Maximum attempts reached.
    Please contact us if the issue persists.

My bad, here is the error in the netlify logs.

3:54:11 PM: ────────────────────────────────────────────────────────────────
3:54:11 PM: 3. @algolia/netlify-plugin-crawler (onSuccess event)
3:54:11 PM: ────────────────────────────────────────────────────────────────
3:54:11 PM: ​
3:54:11 PM: Algolia Netlify plugin started
3:54:11 PM: Sending request to crawl https://crawler.algolia.com/api/1/netlify/crawl
3:54:11 PM: Response {
3:54:11 PM: size: 0,
3:54:11 PM: timeout: 0,
3:54:11 PM: [Symbol(Body internals)]: {
3:54:11 PM: body: PassThrough {
3:54:11 PM: _readableState: [ReadableState],
3:54:11 PM: readable: true,
3:54:11 PM: _events: [Object: null prototype],
3:54:11 PM: _eventsCount: 5,
3:54:11 PM: _maxListeners: undefined,
3:54:11 PM: _writableState: [WritableState],
3:54:11 PM: writable: true,
3:54:11 PM: allowHalfOpen: true,
3:54:11 PM: _transformState: [Object],
3:54:11 PM: [Symbol(kCapture)]: false
3:54:11 PM: },
3:54:11 PM: disturbed: false,
3:54:11 PM: error: null
3:54:11 PM: },
3:54:11 PM: [Symbol(Response internals)]: {
3:54:11 PM: url: ‘https://crawler.algolia.com/api/1/netlify/crawl’,
3:54:11 PM: status: 500,
3:54:11 PM: statusText: ‘Internal Server Error’,
3:54:11 PM: headers: Headers { [Symbol(map)]: [Object: null prototype] },
3:54:11 PM: counter: 0
3:54:11 PM: }
3:54:11 PM: }
3:54:11 PM: Could not reach algolia Error: Internal Server Error {}
3:54:11 PM: at onSuccess (/opt/build/repo/.netlify/plugins/node_modules/@algolia/netlify-plugin-crawler/dist/index.js:107:19)
3:54:11 PM: at processTicksAndRejections (internal/process/task_queues.js:97:5)
3:54:11 PM: at async Object.run (/opt/buildhome/node-deps/node_modules/@netlify/build/src/plugins/child/run.js:20:3)
3:54:11 PM: at async handleEvent (/opt/buildhome/node-deps/node_modules/@netlify/build/src/plugins/child/main.js:36:38)
3:54:11 PM: at async process. (/opt/buildhome/node-deps/node_modules/@netlify/build/src/plugins/ipc.js:103:16)
3:54:11 PM: ​
3:54:11 PM: ────────────────────────────────────────────────────────────────
3:54:11 PM: Plugin “@algolia/netlify-plugin-crawler” failed
3:54:11 PM: ────────────────────────────────────────────────────────────────
3:54:11 PM: ​
3:54:11 PM: Error message
3:54:11 PM: Error: Could not reach Algolia’s Crawler, got: Internal Server Error {}

3:54:11 PM: Plugin details
3:54:11 PM: Package: @algolia/netlify-plugin-crawler
3:54:11 PM: Version: 1.0.0
3:54:11 PM: Repository: git+https://github.com/algolia/algoliasearch-netlify.git
3:54:11 PM: npm link: @algolia/netlify-plugin-crawler - npm
3:54:11 PM: Report issues: Issues · algolia/algoliasearch-netlify · GitHub
3:54:11 PM: ​
3:54:11 PM: Error location
3:54:11 PM: In “onSuccess” event in “@algolia/netlify-plugin-crawler” from Netlify app
3:54:11 PM: at onSuccess (/.netlify/plugins/node_modules/@algolia/netlify-plugin-crawler/dist/index.js:112:21)
3:54:11 PM: ​
3:54:11 PM: Resolved config
3:54:11 PM: build:
3:54:11 PM: command: npm run build
3:54:11 PM: commandOrigin: config
3:54:11 PM: environment:
3:54:11 PM: - ALGOLIA_API_KEY
3:54:11 PM: - ALGOLIA_BASE_URL
3:54:11 PM: publish: /opt/build/repo/_site
3:54:11 PM: publishOrigin: config
3:54:11 PM: plugins:
3:54:11 PM: - inputs: {}
3:54:11 PM: origin: ui
3:54:11 PM: package: ‘@algolia/netlify-plugin-crawler’

The netlify build env keys are in the deploy section put there by the plugin.

Any ideas for a fix?
Thanks
Paul

Hello Paul,

I understand you have trouble triggering the crawl for your site.

What I can see on my side is that Netlify API answer a HTTP 401 when we try to fetch your profile with the auth token we currently have.
I’ll suggest to logout and login again to the Crawler, using Netlify OAuth, to refresh your token. And see if the issue is still present, maybe the token was deleted on Netlify side or is invalid.

If not, you can try to uninstall and reinstall your site, but I don’t think it is coming from that.

Looking forward your answer,

Thanks for the suggestions. I had to delete the OAuth keys and delete the plug-in and re-install. Now it’s working.
Thanks
Paul