updating contract and getting error 404

[Tdawg007]

Version

• Yes

General Question

• No

What happened?

when i go to update my contract using the "npm run update_presale_mint_start_date" and other commands like that, it asks me if this is the date i want to update to and i click y, it gives me the error, "CATCH ERROR: ERROR STATUS: 404

here is what it looks like

PS C:\Users> npm run update_presale_mint_start_date

[email protected] update_presale_mint_start_date
node utils/nftport/updateContract.js -u presale_mint_start_date

Updating presale_mint_start_date to 2022-06-27T16:00:00+00:00, correct? (y/n): y
CATCH ERROR: ERROR STATUS: 404
PS C:\Users>

What have you tried?

i just came here to see if you could help because you guys have been very helpful with my other issues

Relevant log output

No response

Protect your information

• I Agree

[obi-somu]

Paste the contract address into the config file

[Tdawg007]

i got error 422

[sainitin1012]

Pls check whether u have pasted the contract address in ur constant.js file
Check ur nft port key
If u have deployed ur contract more than 5 times ur contract might get frozen
If the above steps are not working finally try to update the contract through nftport website using ur api key over there u can find out what type of error u r facing

[Tdawg007]

how do i update my contract?

[Tdawg007]

and also im on rinkeby to test everything

[sainitin1012]

Hey I tried contacting nftport people what they told is that to update my contract directly through nftport using my api key and contract address even then I got many error, like contract frozen and invalid api key ( like the key is not related to any mentioned contract address) so finally I created another account and forked the repo and used the new acc to generate an api key and now it works but I encountered another error with my front end as my html page is displaying some random values for price of the mint and max supply

…

On Fri, 17 Jun 2022 at 9:58 PM, Tdawg007 ***@***.***> wrote: and also im on rinkeby to test everything — Reply to this email directly, view it on GitHub <#91 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZEJFZVZZ7BFQKTMHVXF2X3VPSRRLANCNFSM5YIRSZIQ> . You are receiving this because you commented.Message ID: ***@***.***>