I used truffle and hardhat to deploy smart contracts on the apothem testnet, everything was working fine a few days ago but suddenly it stopped working
truffle migrate --network apothem
Compiling your contracts...
===========================
<Location>\tradingContractsSystem\build\contracts
> Compiled successfully using:
- solc: 0.8.16+commit.07a7930e.Emscripten.clang
Starting migrations...
======================
> Network name: 'apothem'
> Network id: 51
> Block gas limit: 420000000 (0x1908b100)
1_boss_migration.js
===================
Deploying 'Boss'
----------------
*** Deployment Failed ***
"Boss" -- Unknown Error: <html>
<head><title>500 Internal Server Error</title></head>
<body>
<center><h1>500 Internal Server Error</h1></center>
<hr><center>nginx/1.18.0 (Ubuntu)</center>
</body>
</html>
.
Exiting: Review successful transactions manually by checking the transaction hashes above on Etherscan.
Error: *** Deployment Failed ***
"Boss" -- Unknown Error: <html>
<head><title>500 Internal Server Error</title></head>
<body>
<center><h1>500 Internal Server Error</h1></center>
<hr><center>nginx/1.18.0 (Ubuntu)</center>
</body>
</html>
.
at <Location>\node_modules\truffle\build\webpack:\packages\deployer\src\deployment.js:330:1
Truffle v5.11.5 (core: 5.11.5)
Node v18.19.0
Discussion (7)
Does your codes work on other chains? If this is a problem which only related to xdc chain, you can create an issue on github.com/XinFinOrg/XDPoSChain.
I tested on local ganache, Goerli and mumbai, it works on all of them, so I need to create an issue, thank you.
But am i the only one facing it?
Please create an issue on GitHub and share your codes also. Then we can reproduce your problem.
Hello @sumerrana
We hope that the above issue is resolved, if the issue still persists then please let us know about it so that the team can resolve it on priority. It will be grateful to get an update within 72 hours or else it will be considered resolved.
Thank You.
Hello @sumerrana
Since we haven’t received any response from your side , we are closing the issue as it appears to be resolved. If you still have the issue, please feel free to reopen it.