Error: PollingBlockTracker - encountered an error while attempting to update latest block:
See original GitHub issue- I’ve asked for help in the Truffle Gitter before filing this issue.
Issue
What the issue is, in broad strokes.
Steps to Reproduce
Please provide the shortest amount of steps to reproduce your issue.
Expected Behavior
What you expected to happen.
Actual Results
What actually happened. Please give examples and support it with screenshots, copied output or error messages.
Environment
- Operating System:
- Ethereum client:
- Truffle version (
truffle version
): - node version (
node --version
): - npm version (
npm --version
):
Issue Analytics
- State:
- Created 3 years ago
- Comments:21 (1 by maintainers)
Top Results From Across the Web
Encountered an error while attempting to update latest block
I'm new to blockchain and i was just trying to deploy a simple smart contract to ropsten test net.
Read more >encountered an error while attempting to update latest block ...
Getting following error while deploying using infura. Error: PollingBlockTracker - encountered an error while attempting to update latest block:
Read more >infura - Truffle Migrate Rinkeby - Error: PollingBlockTracker
Truffle Migrate Rinkeby - Error: PollingBlockTracker - encountered an error while attempting to update latest block: Error: ETIMEDOUT.
Read more >Polling.js:51 Uncaught Error: PollingBlockTracker - Moralis
Polling.js:51 Uncaught Error: PollingBlockTracker - encountered an error while attempting to update latest block: undefined.
Read more >pollingblocktracker | The AI Search Engine You Control
const newErr = new Error(`PollingBlockTracker - encountered an error while attempting to update latest block:\n${err.stack}`) ^ Error: PollingBlockTracker ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had the sam issue with BSC testnet. I solved mine by replacing ‘https’ in the provider url with ‘wss’
Please reopen this issue…