Build Failure: "Request is not defined" – Netlify Extensions System Bug (No netlify.toml, no plugins, clean repo)

Support
, ,
1

Hi, I’m experiencing a persistent issue with my site

Error:

Failed retrieving extensions for site XXXXXX-ZZZZZ-YYYYYY-PPPPPPPPP: Request is not defined
Build script returned non-zero exit code: 2

I’m using the lighthouse plugin and I’ve done all the standard troubleshooting steps:

  • Remove/unsinstall/disable all plugins
  • Logged out/in (netlify login)
  • Check netlify status
  • Unlinked and re-linked the repo
  • Retrasnfer the site to my team
  • No netlify.toml
  • No plugins active on the site
  • Build runs locally with netlify build without errors

I suspect the problem started after creating a second site with the same GitHub repo, because we want to migrate to a new url; but this may have corrupted the internal metadata for this site. I tried also contacting support for this case but they wont create a ticket for this issue. This seems to be a Netlify platform bug related to extension resolution.

Is there a way to force a full reset of the internal configuration?
Or can a staff member wipe the broken extension linkage?

Thanks in advance — this seems like a backend problem that needs a real fix.

2

What version of Node.js, Netlify CLI are you using?

3

Same here — it occurs with all commands. In my case, I believe it’s related to running Netlify CLI behind an HTTP/HTTPS proxy. The CLI appears to pick up HTTP_PROXY / HTTPS_PROXY, but every command fails with a fetch failed error while retrieving site extensions.

We’ve tested this with multiple Node.js versions (20, 22, and 25). The logs below correspond to Node 22, which is the currently recommended version.

/srv # node --version
v22.21.1

/srv # ./node_modules/.bin/netlify --version
netlify-cli/23.13.3 linux-x64 node-v22.21.1

/srv # env
HTTPS_PROXY=http://PROXY-IP
NODE_VERSION=22.21.1
HOSTNAME=
YARN_VERSION=1.22.22
SHLVL=1
HOME=/root
OLDPWD=/root
https_proxy=http://:PROXY-IP
http_proxy=http://:PROXY-IP
NETLIFY_AUTH_TOKEN=xxxx
TERM=xterm
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/srv
HTTP_PROXY=http://PROXY-IP

/srv # ./node_modules/.bin/netlify status --debug
[project.ts]: detectFrameworks
[project.ts]: detectBuildSystem
[project.ts]: detectWorkspaces
[project.ts]: detectPackageManager
[project.ts]: detectFrameworksInPath - undefined

❯ Initial build environment
context: dev
cwd: /srv
featureFlags: 

mode: cli
repositoryRoot: /srv
siteId: 
›   Warning: Error: Failed retrieving extensions for site : fetch failed. Double-check your login status with ‘netlify status’ or contact support with details of your error.
›       at getError (file:///srv/node_modules/@netlify/config/lib/error.js:14:16)
›       at throwUserError (file:///srv/node_modules/@netlify/config/lib/error.js:4:20)
›       at getExtensions (file:///srv/node_modules/@netlify/config/lib/api/site_info.js:149:16)
›       at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
›       at async Promise.all (index 2)
›       at async getSiteInfo (file:///srv/node_modules/@netlify/config/lib/api/site_info.js:41:46)
›       at async resolveConfig (file:///srv/node_modules/@netlify/config/lib/main.js:51:33)
›       at async BaseCommand.getConfig (file:///srv/node_modules/netlify-cli/dist/commands/base-command.js:565:20)
›       at async BaseCommand.init (file:///srv/node_modules/netlify-cli/dist/commands/base-command.js:468:30)
›       at async Object.callback (file:///srv/node_modules/netlify-cli/dist/commands/base-command.js:166:13)
›   Warning: Failed to resolve config, falling back to offline resolution

──────────────────────┐
Current Netlify User │
──────────────────────┘
Name:  xxxxxx
Email: xxxxxxx

────────────────────┐
Netlify Project Info  │
────────────────────┘
Admin URL:   undefined
Project URL: undefined
Project Id:  xxxx-xxx-xxx-xxx

Currently, we’re unable to deploy our site with Netlify CLI when HTTP_PROXY / HTTPS_PROXY is set. This may be related to https://github.com/netlify/cli/issues/3115.