Hi everyone, I’m still encountering this issue in MacBook using the default time.apple.com: Error 404 - ingress_expiry not within expected range - #8 by xalkan
How can I fix it? I tried setting the time manually, but the issue keeps coming back.
Hello there @xalkan,
This error (usually) means that your local machine has the wrong time. Have you tried to set your mac time automatically? Have you checked if your computer is set to the correct date and time?
1 Like
Hi Jennifer! Thank you.
Yes, I’m setting the time automatically, but it seems a difference in seconds is causing the error.
1 Like
Hello there,
Thank you for the confirmation. Let me check!
1 Like
To confirm, this is on an application that you are building?
You can support syncTime when using the HttpAgent: https://agent-js.icp.xyz/agent/classes/HttpAgent.html#syncTime. This is a built-in feature if you are using the v.2.0.0 version.
If this is not an application that you built, then you may need to manually change your server time forward by two minutes.
1 Like
Hi Jennifer, thanks for the info! Updating the agent to its latest version on Juno has fixed the sync issue → @junobuild/core-peer@0.0.20-next-2024-07-24 
2 Likes
Hi @jennifertran! All of a sudden, this error came back, tho we are using the agent v2 - what could the reason be?
Hmm, have you tried to set your machine time?
Yes, and after updating the agent to v2, this error went away… so I’m not sure why it came back.
1 Like
Let me check with the team with there is anything else that you can do.
1 Like
The team is working on an update and will follow up when it is done.
Hi there! Could this error come from somewhere else? Now that I’m using the Bitcoin Mainnet canister instead of the Testnet3 one, I’m not getting the error anymore.
I just got this error again, tho the transaction went through on Bitcoin.
1 Like
What is the message that you are trying to send or what are you trying to do in the canister?
Signing with ECDSA to send a Bitcoin transaction.
1 Like
I cannot imagine why it would be different on testnet vs. mainnet. We’ll note it though as we are working on the update. Thank you for the follow-up!
1 Like
I got more info about this error:
1 Like
What’s the solution being worked on? It there an issue or PR to track?
1 Like
Thank you. We are working on an update to improve SyncTime in the AgentJS library.
2 Likes
@xalkan, let’s wait until Agent-js is patched. As soon as it is, I’ll integrate it into Juno’s library or, like last time, release a ‘next’ version for you.
In the meantime, you can maybe try syncing your local clock time to time to see if it resolve the issue?
Note that if you encounter the error while developing against mainnet, you could also switch to local development. Let me know if you need help with that.
2 Likes