[Bug]: Catch Error 429

[gregory3]

Version

• [X] Yes

General Question

• [X] No

What happened?

A bug happened! When the user runs npm run mint.js Computer Response: Ok to mint 1-1? (y/n) User Clicks: y Terminal goes into Catch Error 429 loop

What have you tried?

I Googled and asked the community in the discord server but could not find a solution. With an update 5 days ago it seems too new for others to find.

Relevant log output

run mint --start=1 --end=1

> [email protected] mint      
> node utils/nftport/mint %npm_config_start% %npm_config_end%

OK to mint 1-1? (y/n):


CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429

Protect your information

• [X] I Agree

[ghost]

hi, same issue here : https://github.com/codeSTACKr/create-10k-nft-collection/issues/157

[gregory3]

What have you tried? I thought it was my config file however all my ids are filled out correctly/ When I check if my images are stored with / on ipfs with the deployed contract everything is on the eth.testnet

[ghost]

try to copy the contract address from contract/_contract.json and paste to CONTRACT_ADDRESS in config.js did not work for me but sometimes it works

[tranpham19]

try to copy the contract address from contract/_contract.json and paste to CONTRACT_ADDRESS in config.js did not work for me but sometimes it works

I tried this to mint NFT from 1-10 but it was error like below. After stopping the batch and start again from 8-10 it worked. Mint transaction created for: CAT PAWS #1! Mint transaction created for: CAT PAWS #2! Mint transaction created for: CAT PAWS #3! Mint transaction created for: CAT PAWS #4! Mint transaction created for: CAT PAWS #5! Mint transaction created for: CAT PAWS #6! Mint transaction created for: CAT PAWS #7! CATCH ERROR: ERROR STATUS: 429 Retrying CATCH ERROR: ERROR STATUS: 429 Retrying CATCH ERROR: ERROR STATUS: 429 Retrying CATCH ERROR: ERROR STATUS: 429 Retrying CATCH ERROR: ERROR STATUS: 429

---

OK to mint 8-10? (y/n): y Mint transaction created for: CAT PAWS #8! Mint transaction created for: CAT PAWS #9! Mint transaction created for: CAT PAWS #10! Minting complete. To check for errors run command: npm run check_txns --dir=minted

[cryptovally]

I use those scripts for weeks now. My plan was to mint 200 NFTs per week. So far so good until last week. I was on 1200 and wanted to mint 1201 - 1400. I got the error 429, but the nfts were minted anyhow. strange. Today I did it for 1401 - 1600 and reveice the error 503 and nothing is minted.

I'm pretty sure nftport changed something in the api, but "forgot" to inform their customers :-(

Any info is appreciated

update I updated the retrieveContract.js file in row 30. Now I get error 429 and 503 in random order . Funny thing, then an when is an NFT minted with the response: Minting xxxxxxxxxxxx failed :( Response: OK Error: undefined.

[wolfGT]

This happened to me too when minting "npm run mint --start=1". Reason: I created the contract manually at the nftport website docs using its APIs forms. It seems their forms are not creating the contracts properly.

CATCH ERROR: ERROR STATUS: 404
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 404
Retrying

It worked after I created a contract with "npm run deploy_contract" instead.

[wolfGT]

I use those scripts for weeks now. My plan was to mint 200 NFTs per week. So far so good until last week. I was on 1200 and wanted to mint 1201 - 1400. I got the error 429, but the nfts were minted anyhow. strange. Today I did it for 1401 - 1600 and reveice the error 503 and nothing is minted.

I'm pretty sure nftport changed something in the api, but "forgot" to inform their customers :-(

Any info is appreciated

Now I get error 429 and 503 in random order

About the 503 error, with Rinkeby I kept the previous files open in my IDE (after renaming folders) so the scripts could not replace the new versions. Also happened to me when minting in polygon after successfully minting in rinkeby, the file uploads and metadata scripts show that they are already uploaded, so it seems there is a conflict when switching chains and reusing some data.

[wolfGT]

@cryptovally : Turns out there is a bug with nftpport. Devs are working on it. From their discord today:

[RobsonMaciel]

try to copy the contract address from contract/_contract.json and paste to CONTRACT_ADDRESS in config.js did not work for me but sometimes it works

WOW!! It works for me!!! Thank you very much brooo!!!

[Hatem-shaban]

Copy the contract address from contract/_contract.json and paste it to CONTRACT_ADDRESS in config.js and mint again it worked for me