create-10k-nft-collection
create-10k-nft-collection copied to clipboard
codeSTACKr
[Bug]: Contract deployment failed even though _contract.json and _deployContractResponse.json response "OK", followed by minting errors
Version
- [X] Yes
General Question
- [X] No
What happened?
I followed the instruction in "ULTIMATE Create An ENTIRE NFT Collection (10,000+) & MINT With ZERO Coding Knowledge - PFP Generator" video and had no problems until it came to the deploy contract step. I deployed the contract and the after a bit entered npm run get_contract. It would say 'contract "my project" deployment failed'. I waited a few hours, then overnight but it still says the same thing when I npm run get_contract. But I found under the contract folder there are files _contract.json and _deployContractResponse.json where both responses are "OK", and when I follow the transaction_external_url to etherscan it says status successful on rinkeby. So even though it says deployment failed in the VS Code logs it seems like it has worked. But when I try to go ahead and mint for example npm run mint --start=1 --end=5 then I just get endless CATCH ERROR: ERROR STATUS: 429 Retrying, and some 422 mixed in as well. I feel so close but this has really put a damper on my project I don't know where to go from here. I would appreciate help so much, thanks.
What have you tried?
I Googled and asked the community in the discord server but could not find a solution.
Relevant log output
PS D:\create-10k-nft-collection-2.0.0> npm run get_contract
> [email protected] get_contract
> node utils/nftport/retrieveContract
Contract Tiny Talented Toshi deployment failed
PS D:\create-10k-nft-collection-2.0.0> npm run mint --start=1 --end=5
> [email protected] mint
> node utils/nftport/mint %npm_config_start% %npm_config_end%
OK to mint 1-5? (y/n): y
CATCH ERROR: ERROR STATUS: 422
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: 422
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
CATCH ERROR: ERROR STATUS: 429
Retrying
Protect your information
- [X] I Agree
Man it's so bad...and it feels so close. Please someone should help fix this problem m
No friend. I haven't yet. I'm trying to contact codeSTACKr to get his attention to it
On Mon, May 2, 2022, 6:36 PM ADRIhein2 @.***> wrote:
hi did u find how to fix it ?
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1115159569, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QEVXJ3YAAUMWTJJRAWTVIAHBDANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>
Yup still stuck, no clue about the problem but it a huge bummer. Hope someone with insight of a solution sees this, seems to be a widespread problem considering we all have experienced the same type of error.
Yes it seems so. Let's try to contact the developers quickly so they can resolve this issue.
On Mon, May 2, 2022, 6:51 PM davopolo @.***> wrote:
Good idea, i appreciate that
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1115177998, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QEWYRK4HTBFQIBA5DHTVIAI3ZANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>
i found that : [codeSTACKr] commented [on 25 Jan] "429 is a server error and will require you to retry until successful."
I’ve retried everyday for the last week multiples times a day and same errors so I don’t know if retrying over and over is really a fix unless it’s a server side issue that gets resolved at some point.
i can see that "Contract Tiny Talented Toshi deployment failed" did u see that
Wow...I'll keep trying and trying. I'll get back to you all if anything positive comes up after 50 tries
On Mon, May 2, 2022, 7:11 PM davopolo @.***> wrote:
Yes I did see that, even though the contract and deploy json were created
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1115204794, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QERFFGS6STZ5CROC3ELVIALF3ANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>
I have minted with a different api key, I have tried different options ..even changing the name of my project...still the same error
On Mon, May 2, 2022, 7:15 PM Edegbai Connell @.***> wrote:
Wow...I'll keep trying and trying. I'll get back to you all if anything positive comes up after 50 tries
On Mon, May 2, 2022, 7:11 PM davopolo @.***> wrote:
Yes I did see that, even though the contract and deploy json were created
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1115204794, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QERFFGS6STZ5CROC3ELVIALF3ANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>
Thanks. Yeah it’s just the weirdest thing. Everything was just so smooth until this. It sucks
It really sucks. I tested it on rinkeby and every single thing worked fine....but now.... issues...lol
On Mon, May 2, 2022, 7:18 PM davopolo @.***> wrote:
Thanks. Yeah it’s just the weirdest thing. Everything was just so smooth until this. It sucks
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1115211355, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QEXBGYSMUP5QOIA3RSTVIAL5XANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>
I guess my question is, has anyone successfully used this method to mint in the last week? Is everyone having this issue since then or just a few of us unlucky ones
Workaround: Once you run get_contract copy the contract address from contract/_contract.json and set that to CONTRACT_ADDRESS in the config.js. Then run the mint command.
Will do, thanks! I hope it works out
On Tue, May 3, 2022, 5:54 PM wrightp @.***> wrote:
Workaround: Once you run get_contract copy the contract address from contract/_contract.json and set that to CONTRACT_ADDRESS in the config.js. Then run the mint command.
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1116328370, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QEQZVCCQL4X5KCO3BSTVIFK5ZANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>
Hey folks! codeSTACKr just replied to my comment in the Youtube video and he mentioned that he uploaded a new version of this repo fixing this issue, it looks like NFTPort made some changes in the way that the errors are handled. Hope that helps!
Antonella Saccone
De: blackmuller @.> Enviado: Tuesday, May 3, 2022 3:00:22 PM Para: codeSTACKr/create-10k-nft-collection @.> Cc: Antonella Saccone @.>; Manual @.> Asunto: [External] Re: [codeSTACKr/create-10k-nft-collection] [Bug]: Contract deployment failed even though _contract.json and _deployContractResponse.json response "OK", followed by minting errors (Issue #157)
Will do, thanks! I hope it works out
On Tue, May 3, 2022, 5:54 PM wrightp @.***> wrote:
Workaround: Once you run get_contract copy the contract address from contract/_contract.json and set that to CONTRACT_ADDRESS in the config.js. Then run the mint command.
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1116328370, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QEQZVCCQL4X5KCO3BSTVIFK5ZANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FcodeSTACKr%2Fcreate-10k-nft-collection%2Fissues%2F157%23issuecomment-1116388535&data=05%7C01%7Cantonella.saccone%40rga.com%7Cee8b724aaabe41aec6c508da2d2ecb6e%7C9725079efc4f44a4b797aa982bff3996%7C0%7C0%7C637871976262415489%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zUVZLnVv5ZSgazvr0Fgd9lP%2BHD6KhDXmV7JdB8W3jOg%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAY46R2VCHKLQFUTBBFL2F7DVIFSTNANCNFSM5UTGA67A&data=05%7C01%7Cantonella.saccone%40rga.com%7Cee8b724aaabe41aec6c508da2d2ecb6e%7C9725079efc4f44a4b797aa982bff3996%7C0%7C0%7C637871976262415489%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ldIImFEBBZXmzpO4pRDBtHAVZKIvetdb%2Fdhj%2B3OGvbQ%3D&reserved=0. You are receiving this because you are subscribed to this thread.Message ID: @.***>
R/GA We design businesses and brands for a more human future
Uriarte 1572 (C1414DAP), Ciudad de Buenos Aires, Argentina www.rga.comhttp://www.rga.com www.twitter.com/rgahttp://www.twitter.com/rga www.facebook.com/rgahttp://www.facebook.com/rga
This message contains information which may be confidential and privileged. Unless you are the intended recipient (or are authorized to receive this message on behalf of the intended recipient), you may not copy, disseminate, or disclose this message or any information contained in this message. If you have received this message in error, please notify the sender by reply e-mail or forward the message to @.*** and delete the message. Thank you very much.
Well now my contract has deployed successfully after changing that line of code. However now this is whats happening now that ive tried to mint... They exist under the minted folder in json format, they show up on etherscan as successful mints under the rinkeby network, but appear on my opensea testnet as blank images. Two steps forward, one step back it seems.
Contract Tiny Talented Toshi deployed successfully PS D:\create-10k-nft-collection-2.0.0> npm run mint --start=1 --end=5
[email protected] mint node utils/nftport/mint %npm_config_start% %npm_config_end%
OK to mint 1-5? (y/n): y Minting Toshi Egg #1 failed :( Response: OK Error: undefined Minting Toshi Egg #2 failed :( Response: OK Error: undefined Minting Toshi Egg #3 failed :( Response: OK Error: undefined Minting Toshi Egg #4 failed :( Response: OK Error: undefined Minting Toshi Egg #5 failed :( Response: OK Error: undefined Minting complete. To check for errors run command: npm run check_txns --dir=minted PS D:\create-10k-nft-collection-2.0.0> npm run check_txns --dir=minted
[email protected] check_txns node utils/nftport/checkTxns %npm_config_dir%
Checking transactions... Edition #1: Transaction failed Edition #2: Transaction failed Edition #3: Transaction failed Edition #4: Transaction failed Edition #5: Transaction failed All transactions checked. Failed Txn Count: 5 Failed Txns: 1,2,3,4,5
Good! We are moving forward I guess. Meanwhile I can't wait to buy Toshi Eggs!!!! Hahahah...☺️☺️☺️☺️
On Tue, May 3, 2022, 7:59 PM davopolo @.***> wrote:
Well now my contract has deployed successfully after changing that line of code. However now this is whats happening now that ive tried to mint... They exist under the minted folder in json format, they show up on etherscan as successful mints under the rinkeby network, but appear on my opensea testnet as blank images. Two steps forward, one step back it seems.
Contract Tiny Talented Toshi deployed successfully PS D:\create-10k-nft-collection-2.0.0> npm run mint --start=1 --end=5
@.*** mint node utils/nftport/mint %npm_config_start% %npm_config_end%
OK to mint 1-5? (y/n): y Minting Toshi Egg #1 https://github.com/codeSTACKr/create-10k-nft-collection/issues/1 failed :( Response: OK Error: undefined Minting Toshi Egg #2 https://github.com/codeSTACKr/create-10k-nft-collection/issues/2 failed :( Response: OK Error: undefined Minting Toshi Egg #3 https://github.com/codeSTACKr/create-10k-nft-collection/issues/3 failed :( Response: OK Error: undefined Minting Toshi Egg #4 https://github.com/codeSTACKr/create-10k-nft-collection/issues/4 failed :( Response: OK Error: undefined Minting Toshi Egg #5 https://github.com/codeSTACKr/create-10k-nft-collection/issues/5 failed :( Response: OK Error: undefined Minting complete. To check for errors run command: npm run check_txns --dir=minted PS D:\create-10k-nft-collection-2.0.0> npm run check_txns --dir=minted
@.*** check_txns node utils/nftport/checkTxns %npm_config_dir%
Checking transactions... Edition #1 https://github.com/codeSTACKr/create-10k-nft-collection/issues/1: Transaction failed Edition #2 https://github.com/codeSTACKr/create-10k-nft-collection/issues/2: Transaction failed Edition #3 https://github.com/codeSTACKr/create-10k-nft-collection/issues/3: Transaction failed Edition #4 https://github.com/codeSTACKr/create-10k-nft-collection/issues/4: Transaction failed Edition #5 https://github.com/codeSTACKr/create-10k-nft-collection/issues/5: Transaction failed All transactions checked. Failed Txn Count: 5 Failed Txns: 1,2,3,4,5
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1116454426, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QERQ3AS2ZUTE62NK6UTVIFZPTANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>
Where did he upload it? I checked GitHub and it was still version 2.0.0 that's there
On Tue, May 3, 2022, 7:04 PM Antonella Saccone @.***> wrote:
Hey folks! codeSTACKr just replied to my comment in the Youtube video and he mentioned that he uploaded a new version of this repo fixing this issue, it looks like NFTPort made some changes in the way that the errors are handled. Hope that helps!
Antonella Saccone
De: blackmuller @.> Enviado: Tuesday, May 3, 2022 3:00:22 PM Para: codeSTACKr/create-10k-nft-collection @.> Cc: Antonella Saccone @.>; Manual @.> Asunto: [External] Re: [codeSTACKr/create-10k-nft-collection] [Bug]: Contract deployment failed even though _contract.json and _deployContractResponse.json response "OK", followed by minting errors (Issue #157)
Will do, thanks! I hope it works out
On Tue, May 3, 2022, 5:54 PM wrightp @.***> wrote:
Workaround: Once you run get_contract copy the contract address from contract/_contract.json and set that to CONTRACT_ADDRESS in the config.js. Then run the mint command.
— Reply to this email directly, view it on GitHub < https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1116328370 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AOV2QEQZVCCQL4X5KCO3BSTVIFK5ZANCNFSM5UTGA67A
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub< https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FcodeSTACKr%2Fcreate-10k-nft-collection%2Fissues%2F157%23issuecomment-1116388535&data=05%7C01%7Cantonella.saccone%40rga.com%7Cee8b724aaabe41aec6c508da2d2ecb6e%7C9725079efc4f44a4b797aa982bff3996%7C0%7C0%7C637871976262415489%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zUVZLnVv5ZSgazvr0Fgd9lP%2BHD6KhDXmV7JdB8W3jOg%3D&reserved=0>, or unsubscribe< https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAY46R2VCHKLQFUTBBFL2F7DVIFSTNANCNFSM5UTGA67A&data=05%7C01%7Cantonella.saccone%40rga.com%7Cee8b724aaabe41aec6c508da2d2ecb6e%7C9725079efc4f44a4b797aa982bff3996%7C0%7C0%7C637871976262415489%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ldIImFEBBZXmzpO4pRDBtHAVZKIvetdb%2Fdhj%2B3OGvbQ%3D&reserved=0
. You are receiving this because you are subscribed to this thread.Message ID: @.***>
R/GA We design businesses and brands for a more human future
Uriarte 1572 (C1414DAP), Ciudad de Buenos Aires, Argentina www.rga.comhttp://www.rga.com www.twitter.com/rga< http://www.twitter.com/rga> www.facebook.com/rga< http://www.facebook.com/rga>
This message contains information which may be confidential and privileged. Unless you are the intended recipient (or are authorized to receive this message on behalf of the intended recipient), you may not copy, disseminate, or disclose this message or any information contained in this message. If you have received this message in error, please notify the sender by reply e-mail or forward the message to @.*** and delete the message. Thank you very much.
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1116391939, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QERLMAGIT3ZFTN47ANLVIFTBLANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>
Great notes guys. I am going to try right now. Side question does my wallet need to have money before I do the minting?
After minting were failed and I checked the transactions....I went on opensea and saw my complete images uploaded. But I never knew with polygon we still have to pay gas fees for selling functionality and some other fees ...wow.
On Wed, May 4, 2022, 8:08 PM gregory3 @.***> wrote:
Great notes guys. I am going to try right now. Side question does my wallet need to have money before I do the minting?
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1117714178, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QEWUZXIZGM4EFCDNQW3VILDMDANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>
I just copied the contract address and put it in the code...then tried minting again. Transactions were not successful but they showed up on opensea. Don't know if I should go ahead and sell.
On Wed, May 4, 2022, 8:58 PM ADRIhein2 @.***> wrote:
how did u fix 429 ERROR issue ?
— Reply to this email directly, view it on GitHub https://github.com/codeSTACKr/create-10k-nft-collection/issues/157#issuecomment-1117822183, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOV2QERAQJ4HFH2BIWRVH53VILJGRANCNFSM5UTGA67A . You are receiving this because you commented.Message ID: @.***>