# Ingress expiry issue **URL:** \ **Category:** Developers\ **Created:** [July 19, 2024, 6:42pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416 "2024-07-19T18:42:35Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)\ **Post date:** [July 19, 2024, 6:42pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/1 "2024-07-19T18:42:36Z")
Hi everyone, I’m still encountering this issue in MacBook using the default [time.apple.com](http://time.apple.com): [Error 404 - ingress\_expiry not within expected range - #8 by xalkan](https://forum.dfinity.org/t/error-404-ingress-expiry-not-within-expected-range/19803/8) How can I fix it? I tried setting the time manually, but the issue keeps coming back. ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/c/4/c4d2e41513ee627870cec0312e805b5e52211303.png) ---
**Author:** ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)\ **Post date:** [July 19, 2024, 6:57pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/2 "2024-07-19T18:57:21Z")
Hello there @xalkan, This error (usually) means that your local machine has the wrong time. Have you tried to set your [mac time automatically](https://support.apple.com/guide/mac-help/set-the-date-and-time-automatically-mchlp2996/)? Have you checked if your computer is set to the correct date and time? ---
**Author:** ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)\ **Post date:** [July 19, 2024, 7:23pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/3 "2024-07-19T19:23:12Z")
Hi Jennifer! Thank you. Yes, I’m setting the time automatically, but it seems a difference in seconds is causing the error. ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/c/f/cf701f954d55677c0cc743ad4c84a2988ad68388.png) ---
**Author:** ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)\ **Post date:** [July 19, 2024, 8:26pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/4 "2024-07-19T20:26:17Z")
Hello there, Thank you for the confirmation. Let me check! ---
**Author:** ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)\ **Post date:** [July 20, 2024, 1:15am UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/5 "2024-07-20T01:15:31Z")
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](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. ---
**Author:** ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)\ **Post date:** [July 29, 2024, 8:45pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/6 "2024-07-29T20:45:53Z")
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 🙏 ---
**Author:** ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)\ **Post date:** [August 27, 2024, 7:53pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/7 "2024-08-27T19:53:38Z")
Hi @jennifertran! All of a sudden, this error came back, tho we are using the agent v2 - what could the reason be? ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/3/3/33f82b85305416e816b713ce305e1c6a82074410.png) ---
**Author:** ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)\ **Post date:** [August 28, 2024, 7:33am UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/8 "2024-08-28T07:33:52Z")
Hmm, have you tried to set your machine time? ---
**Author:** ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)\ **Post date:** [August 29, 2024, 6:11pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/9 "2024-08-29T18:11:58Z")
Yes, and after updating the agent to v2, this error went away… so I’m not sure why it came back. ---
**Author:** ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)\ **Post date:** [August 29, 2024, 7:29pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/10 "2024-08-29T19:29:31Z")
Let me check with the team with there is anything else that you can do. ---
**Author:** ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)\ **Post date:** [August 30, 2024, 9:35pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/11 "2024-08-30T21:35:57Z")
The team is working on an update and will follow up when it is done. ---
**Author:** ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)\ **Post date:** [September 3, 2024, 7:59pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/12 "2024-09-03T19:59:04Z")
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. ---
**Author:** ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)\ **Post date:** [September 3, 2024, 9:15pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/13 "2024-09-03T21:15:00Z")
I just got this error again, tho the transaction went through on Bitcoin. ---
**Author:** ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)\ **Post date:** [September 4, 2024, 5:44pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/14 "2024-09-04T17:44:01Z")
What is the message that you are trying to send or what are you trying to do in the canister? ---
**Author:** ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)\ **Post date:** [September 4, 2024, 5:55pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/15 "2024-09-04T17:55:33Z")
Signing with ECDSA to send a Bitcoin transaction. ---
**Author:** ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)\ **Post date:** [September 4, 2024, 6:46pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/16 "2024-09-04T18:46:53Z")
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! ---
**Author:** ![xalkan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/xalkan/32/16076_2.png) [@xalkan](https://forum.dfinity.org/u/xalkan)\ **Post date:** [September 6, 2024, 5:51pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/17 "2024-09-06T17:51:36Z")
I got more info about this error: ![Screenshot 2024-09-06 at 02.38.27](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/7/b/7bfa53f72ad172d647c21e2db0c2b376ea842833.png) ---
**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\ **Post date:** [September 6, 2024, 6:05pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/18 "2024-09-06T18:05:25Z")
> [@jennifertran](#): > > working on the update What’s the solution being worked on? It there an issue or PR to track? ---
**Author:** ![jennifertran](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jennifertran/32/11558_2.png) [@jennifertran](https://forum.dfinity.org/u/jennifertran)\ **Post date:** [September 6, 2024, 6:42pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/19 "2024-09-06T18:42:33Z")
Thank you. We are working on an update to improve `SyncTime` in the AgentJS library. ---
**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\ **Post date:** [September 6, 2024, 6:55pm UTC](https://forum.dfinity.org/t/ingress-expiry-issue/33416/20 "2024-09-06T18:55:06Z")
@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. [Next page](https://forum.dfinity.org/t/ingress-expiry-issue/33416.md?page=2)