Exit code 128 during build failed

I know it’s already been asked but relinking my to another repo doesn’t seem to be fixing the issue… I don’t have a URL because it hasn’t been deployed yet :frowning:

Here’s my build settings

Here’s my log:

6:01:14 PM: Waiting for other deploys from your team to complete. Check the queue: https://app.netlify.com/teams/5mars/builds
6:01:31 PM: build-image version: 1ca34a93198b041e44214013884c57d146a23fed (focal)
6:01:31 PM: build-image tag: v4.16.4
6:01:31 PM: buildbot version: 2577a19e1559072eeb7a6727cec389b63b90401c
6:01:32 PM: Building without cache
6:01:32 PM: Starting to prepare the repo for build
6:01:32 PM: No cached dependencies found. Cloning fresh repo
6:01:32 PM: git clone --filter=blob:none --no-checkout https://github.com/5mars/crowdfundingWeb3
6:01:32 PM: Preparing Git Reference refs/heads/main
6:01:33 PM: Parsing package.json dependencies
6:01:34 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'client/dist' versus 'dist' in the Netlify UI
6:01:34 PM: Starting build script
6:01:34 PM: Installing dependencies
6:01:34 PM: Python version set to 2.7
6:01:35 PM: v16.19.0 is already installed.
6:01:35 PM: Now using node v16.19.0 (npm v8.19.3)
6:01:35 PM: Enabling Node.js Corepack
6:01:35 PM: Started restoring cached build plugins
6:01:35 PM: Finished restoring cached build plugins
6:01:35 PM: Attempting Ruby version 2.7.2, read from environment
6:01:36 PM: Using Ruby version 2.7.2
6:01:36 PM: Using PHP version 8.0
6:01:36 PM: Started restoring cached corepack dependencies
6:01:36 PM: mv: cannot move '/opt/build/cache/.node/corepack' to '/opt/buildhome/.node/corepack': No such file or directory
6:01:36 PM: Finished restoring cached corepack dependencies
6:01:36 PM: Started restoring cached yarn cache
6:01:36 PM: Finished restoring cached yarn cache
6:01:36 PM: No yarn workspaces detected
6:01:36 PM: Started restoring cached node modules
6:01:36 PM: Finished restoring cached node modules
6:01:36 PM: Installing npm packages using Yarn version 1.22.19
6:01:37 PM: yarn install v1.22.19
6:01:37 PM: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
6:01:37 PM: [1/4] Resolving packages...
6:01:37 PM: [2/4] Fetching packages...
6:01:43 PM: error Command failed.
6:01:43 PM: Exit code: 128
6:01:43 PM: Command: git
6:01:43 PM: Arguments: ls-remote --tags --heads ssh://git@github.com/ethereumjs/ethereumjs-abi.git
6:01:43 PM: Directory: /opt/build/repo/client
6:01:43 PM: Output:
6:01:43 PM: Host key verification failed.
6:01:43 PM: fatal: Could not read from remote repository.
6:01:43 PM: Please make sure you have the correct access rights
6:01:43 PM: and the repository exists.
6:01:43 PM: info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
6:02:03 PM: Error during Yarn install
6:02:03 PM: Build was terminated: Build script returned non-zero exit code: 1
6:02:03 PM: Failing build: Failed to build site
6:02:03 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1 (https://ntl.fyi/exit-code-1)
6:02:03 PM: Finished processing build request in 31.449s

Also I don’t know if it’s worth mentionning but when I do npm run dev on my local client file I get this Vite.js warning telling me that maybe a file might be too large or something ? (Some chunks of code are larger than 500kiB blabla …)

Hi @5_mars :wave:t6: ,

Welcome to the forums! :netliconfetti:

Did you fix this? Also can you give this support guide a read?

Hello, no unfortunately… And that’s the support guide I was referring to lol. I did try unlink it and link it back to my repo but didn’t work :\ I could maybe create a totally new one from scratch but not quite sure how to transfert one repo to another :\

That’s the message I get when I npm run build my local file (don’t know if it has something to do with the 128 error):

This error means you don’t have access to the destination repo. Since this is happening during yarn install, I assume you might be using a dependency from Git. You should make sure Netlify can access the private Git repo that you’re using as a module.

Thanks for the reply! Really appreciate it. I’m kind of new in this domain. My root folder contains a .git folder (not quite sure why it’s there), a classic client folder and a backend folder (named web3 because it runs on ETH’s blockchain).

Here’s my dependencies on the client file, i’m not quite sure what the problem might be :\

Hi sorry to ask but can you share the site name/slug you are referring to so we can look on our end?

Yes for sure here it is :


Based on this: Netlify App, it appears one of your dependencies might be using Git to install the modules. Maybe the repo is private, which is why it fails. Try installing it from npm: ethereumjs-abi - npm