Is it possible to opt back out of the new experience? It seems to have broken the algolia-netlify plugin
opened 03:07PM - 22 Nov 22 UTC
closed 12:23PM - 05 Jan 23 UTC
Hi, I'm struggling to get this working with Nuxt site on Netlify, any ideas whe⦠re I'm going wrong? I
My netlify environment variables are
```
ALGOLIA_APPLICATION_ID=YAPTTJ1SIG
ALGOLIA_BASE_URL=https://crawler.algolia.com
ALGOLIA_API_KEY=(secret)
```
My netlify.toml includes the following
```
[[plugins]]
package = "@algolia/netlify-plugin-crawler"
[plugins.inputs]
branches = ['production']
```
The error in the netlify build
```bash
2:47:04 PM: ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
2:47:04 PM: 5. @algolia/netlify-plugin-crawler (onSuccess event)
2:47:04 PM: ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
2:47:04 PM: β
2:47:04 PM: Algolia Netlify plugin started
2:47:04 PM: Sending request to crawl https://crawler.algolia.com/api/1/netlify/crawl
2:47:05 PM: Response {
2:47:05 PM: size: 0,
2:47:05 PM: timeout: 0,
2:47:05 PM: [Symbol(Body internals)]: {
2:47:05 PM: body: PassThrough {
2:47:05 PM: _readableState: [ReadableState],
2:47:05 PM: _events: [Object: null prototype],
2:47:05 PM: _eventsCount: 5,
2:47:05 PM: _maxListeners: undefined,
2:47:05 PM: _writableState: [WritableState],
2:47:05 PM: allowHalfOpen: true,
2:47:05 PM: [Symbol(kCapture)]: false,
2:47:05 PM: [Symbol(kCallback)]: null
2:47:05 PM: },
2:47:05 PM: disturbed: false,
2:47:05 PM: error: null
2:47:05 PM: },
2:47:05 PM: [Symbol(Response internals)]: {
2:47:05 PM: url: 'https://crawler.algolia.com/api/1/netlify/crawl',
2:47:05 PM: status: 403,
2:47:05 PM: statusText: 'Forbidden',
2:47:05 PM: headers: Headers { [Symbol(map)]: [Object: null prototype] },
2:47:05 PM: counter: 0
2:47:05 PM: }
2:47:05 PM: }
2:47:05 PM: Could not reach algolia Error: Forbidden {}
2:47:05 PM: at onSuccess (/opt/build/repo/.netlify/plugins/node_modules/@algolia/netlify-plugin-crawler/dist/index.js:107:19)
2:47:05 PM: at processTicksAndRejections (node:internal/process/task_queues:96:5)
2:47:05 PM: at async Object.run (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/child/run.js:14:5)
2:47:05 PM: at async handleEvent (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/child/main.js:28:42)
2:47:05 PM: at async process.<anonymous> (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/ipc.js:91:24)
2:47:05 PM: β
2:47:05 PM: ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
2:47:05 PM: Plugin "@algolia/netlify-plugin-crawler" failed
2:47:05 PM: ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
2:47:05 PM: β
2:47:05 PM: Error message
2:47:05 PM: Error: Could not reach Algolia's Crawler, got: Forbidden {}
β
2:47:05 PM: Plugin details
2:47:05 PM: Package: @algolia/netlify-plugin-crawler
2:47:05 PM: Version: 1.0.0
2:47:05 PM: Repository: git+https://github.com/algolia/algoliasearch-netlify.git
2:47:05 PM: npm link: https://www.npmjs.com/package/@algolia/netlify-plugin-crawler
2:47:05 PM: Report issues: https://github.com/algolia/algoliasearch-netlify/issues
2:47:05 PM: β
2:47:05 PM: Error location
2:47:05 PM: In "onSuccess" event in "@algolia/netlify-plugin-crawler" from netlify.toml
2:47:05 PM: β
2:47:05 PM: Resolved config
2:47:05 PM: build:
2:47:05 PM: command: nuxt generate
2:47:05 PM: commandOrigin: ui
2:47:05 PM: environment:
2:47:05 PM: - ADMIN_PASSWORD
2:47:05 PM: - ADMIN_SERVER_PASSWORD
2:47:05 PM: - ADMIN_USERNAME
2:47:05 PM: - ALGOLIA_API_KEY
2:47:05 PM: - ALGOLIA_APPLICATION_ID
2:47:05 PM: - ALGOLIA_BASE_URL
```
1 Like
akang10
November 24, 2022, 6:11pm
2
Same, broken for us. Horrible
It was the new env vars experience. I requested netlify support to roll back to the old experience, removed all Algolia env vars, deleted and re-installed the app and itβs working again.
Thatβs not completely true.
As you had linked the issue:
opened 03:07PM - 22 Nov 22 UTC
closed 12:23PM - 05 Jan 23 UTC
Hi, I'm struggling to get this working with Nuxt site on Netlify, any ideas whe⦠re I'm going wrong? I
My netlify environment variables are
```
ALGOLIA_APPLICATION_ID=YAPTTJ1SIG
ALGOLIA_BASE_URL=https://crawler.algolia.com
ALGOLIA_API_KEY=(secret)
```
My netlify.toml includes the following
```
[[plugins]]
package = "@algolia/netlify-plugin-crawler"
[plugins.inputs]
branches = ['production']
```
The error in the netlify build
```bash
2:47:04 PM: ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
2:47:04 PM: 5. @algolia/netlify-plugin-crawler (onSuccess event)
2:47:04 PM: ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
2:47:04 PM: β
2:47:04 PM: Algolia Netlify plugin started
2:47:04 PM: Sending request to crawl https://crawler.algolia.com/api/1/netlify/crawl
2:47:05 PM: Response {
2:47:05 PM: size: 0,
2:47:05 PM: timeout: 0,
2:47:05 PM: [Symbol(Body internals)]: {
2:47:05 PM: body: PassThrough {
2:47:05 PM: _readableState: [ReadableState],
2:47:05 PM: _events: [Object: null prototype],
2:47:05 PM: _eventsCount: 5,
2:47:05 PM: _maxListeners: undefined,
2:47:05 PM: _writableState: [WritableState],
2:47:05 PM: allowHalfOpen: true,
2:47:05 PM: [Symbol(kCapture)]: false,
2:47:05 PM: [Symbol(kCallback)]: null
2:47:05 PM: },
2:47:05 PM: disturbed: false,
2:47:05 PM: error: null
2:47:05 PM: },
2:47:05 PM: [Symbol(Response internals)]: {
2:47:05 PM: url: 'https://crawler.algolia.com/api/1/netlify/crawl',
2:47:05 PM: status: 403,
2:47:05 PM: statusText: 'Forbidden',
2:47:05 PM: headers: Headers { [Symbol(map)]: [Object: null prototype] },
2:47:05 PM: counter: 0
2:47:05 PM: }
2:47:05 PM: }
2:47:05 PM: Could not reach algolia Error: Forbidden {}
2:47:05 PM: at onSuccess (/opt/build/repo/.netlify/plugins/node_modules/@algolia/netlify-plugin-crawler/dist/index.js:107:19)
2:47:05 PM: at processTicksAndRejections (node:internal/process/task_queues:96:5)
2:47:05 PM: at async Object.run (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/child/run.js:14:5)
2:47:05 PM: at async handleEvent (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/child/main.js:28:42)
2:47:05 PM: at async process.<anonymous> (file:///opt/buildhome/node-deps/node_modules/@netlify/build/lib/plugins/ipc.js:91:24)
2:47:05 PM: β
2:47:05 PM: ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
2:47:05 PM: Plugin "@algolia/netlify-plugin-crawler" failed
2:47:05 PM: ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
2:47:05 PM: β
2:47:05 PM: Error message
2:47:05 PM: Error: Could not reach Algolia's Crawler, got: Forbidden {}
β
2:47:05 PM: Plugin details
2:47:05 PM: Package: @algolia/netlify-plugin-crawler
2:47:05 PM: Version: 1.0.0
2:47:05 PM: Repository: git+https://github.com/algolia/algoliasearch-netlify.git
2:47:05 PM: npm link: https://www.npmjs.com/package/@algolia/netlify-plugin-crawler
2:47:05 PM: Report issues: https://github.com/algolia/algoliasearch-netlify/issues
2:47:05 PM: β
2:47:05 PM: Error location
2:47:05 PM: In "onSuccess" event in "@algolia/netlify-plugin-crawler" from netlify.toml
2:47:05 PM: β
2:47:05 PM: Resolved config
2:47:05 PM: build:
2:47:05 PM: command: nuxt generate
2:47:05 PM: commandOrigin: ui
2:47:05 PM: environment:
2:47:05 PM: - ADMIN_PASSWORD
2:47:05 PM: - ADMIN_SERVER_PASSWORD
2:47:05 PM: - ADMIN_USERNAME
2:47:05 PM: - ALGOLIA_API_KEY
2:47:05 PM: - ALGOLIA_APPLICATION_ID
2:47:05 PM: - ALGOLIA_BASE_URL
```
Itβs happening because Algolia is not natively using Netlifyβs environment variables as mentioned by:
We donβt expose them in the UI on our side.
They have their own non-standard setup which is not compatible with the new experience. So, as it turns out, itβs a pending work on their end to add support for this new feature.
If I wasnβt forced into using the new env vars experience in the UI to access the env vars then it would have continued to work fine, rather than breaking my plugins
fool
November 28, 2022, 7:16pm
7
Hi Felix,
As far as we can tell, nobody forced you to use the new environment variables experience. You, Felix, are the one who opted in on 21 Nov according to the Audit log for your team. I understand that you donβt like how the experience worked and our devs and product team are considering your feedback and how we could improve the experience.
Theyβll see any more actionable feedback you have like βI wish netlify had XYZβd with this changeβ if youβd like to leave any more.
Otherwise, as far as addressing your immediate technical concerns, we can opt you or anyone else, who is blocked, back out of the experience for the time being, if that would unblock you while Algolia or other teams such as your dev team, work to add support for the new settings at Netlify to their plugins.
Thank you for your help rolling back! It certainly fixed my problem.
I had to change a potentially compromised environment variable, can you explain how to do that on this screen, in case I need to for any other of my sites? I used to be able to edit them on this screen. Thanks!
Hi,
It isnβt obvious, but you can do this from βBuildd & deployβ β βEnviromentβ
2 Likes
Perfect! Thatβs very useful to know, thank you!
1 Like
hillary
November 29, 2022, 5:26pm
11
Thanks for sharing, @negentropics
crimcol
December 8, 2022, 11:01pm
12
May I request to roll back me to previous experience?
I have the same issue with Algolia.
We can only do that if we know the site name.
Can I please be opted out of this new experience. Similar to other commenters, the Algolia plugin is now broken on my site.
Site: ketanvijayvargiya.com .
luke
December 29, 2022, 7:51am
15
Hi, @eba9280d263e58958b1f . The site has been opted out of the new environment variables.
If there are other questions or concerns, please let us know.
Can I please be opted out of this new experience. Similar to other commenters, the Algolia plugin is now broken on my site.
delikatesses.se
Can I please be opted out of this new experience. Similar to other commenters, the Algolia plugin is now broken on my site.
Site: https://spigot-mc.netlify.app
Hi everyone, the Algolia Netlify plugin has been adapted to work with the new environment variables experience! Sorry for the troubles!
Just to clarify a couple of things regarding the plugin:
Setting environment variables at the Site level was the standard setup when the plugin was developed, the fact that the env vars arenβt shown in the Algolia UI is not related. The problem is that the plugin calls the API endpoints directly without using the API Client, and the API endpoints have changed with the new experience.
But the new sites were forced to use it, so the problem was real. Thatβs actually great that a few users tested it and were able to find out that the plugin was not compatible with it before everyone gets migrated! thanks again
May I also have mine rolled back as well?
Thank you!!