# Ingress\_expiry not within expected range error **URL:** \ **Category:** Motoko\ **Tags:** Functional-Programming, community-consideration, Frontend\ **Created:** [September 23, 2024, 1:03pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456 "2024-09-23T13:03:28Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\ **Post date:** [September 27, 2024, 1:53pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/22 "2024-09-27T13:53:16Z")
We are not 100% but, there might be a bug. So if anyone can give a hand test an hypothesis please follow-up there: > [@Ingress Expiry Issue - Your Input Needed!](https://forum.dfinity.org/t/ingress-expiry-issue-your-input-needed/35609): > > Hi everyone wave, Over the past few weeks, there have been several reports on the forum from devs encountering ingress expiry issues, such as the following: Error: ReplicaTimeError: Specified ingress\_expiry not within expected range: Minimum allowed expiry: 2024-09-25 13:57:00.580809774 UTC, Maximum allowed expiry: 2024-09-25 14:02:30.580809774 UTC, Provided expiry: 2024-09-25 13:57:00 UTC While we provided some valid explanations and future improvements in various threads yesterday (for … ---
**Author:** ![dantol29](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dantol29/32/20601_2.png) [@dantol29](https://forum.dfinity.org/u/dantol29)\ **Post date:** [September 27, 2024, 1:59pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/23 "2024-09-27T13:59:05Z")
It does not fix the problem… ---
**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\ **Post date:** [September 27, 2024, 2:02pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/24 "2024-09-27T14:02:35Z")
A pity 😕. Can you share your more details, like source code (if open source) and link to your app on mainnet? Assuming my colleagues may be interested to have a look. ---
**Author:** ![dantol29](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dantol29/32/20601_2.png) [@dantol29](https://forum.dfinity.org/u/dantol29)\ **Post date:** [September 27, 2024, 2:08pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/25 "2024-09-27T14:08:59Z")
Not open source for now, sorry( I am developing ledger scanner and it has to constantly call `get_blocks` or `get_transactions`. I noticed that every ~20 minutes this issue appears. My program automatically restarts broken process and requests work fine for ~20 minutes. I send the source code here: [Ingress Expiry Issue - Your Input Needed!](https://forum.dfinity.org/t/ingress-expiry-issue-your-input-needed/35609) ---
**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\ **Post date:** [September 27, 2024, 2:13pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/26 "2024-09-27T14:13:01Z")
Thanks. I have share your feedback. ---
**Author:** ![Alishan](https://avatars.discourse-cdn.com/v4/letter/a/d6d6ee/32.png) [@Alishan](https://forum.dfinity.org/u/Alishan)\ **Post date:** [September 30, 2024, 10:01am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/27 "2024-09-30T10:01:54Z")
@YAP @peterparker@jennifertran my website is about article when i try to publish the article then i face this error but when i change i pc time 1 mint up then its published and when i set it automatically then i face this error , issue is that mostly preople in world has time automatically set and i can’t ask all of them to set there time 1 mint up, kindly solve this error, Specified ingress\_expiry not within expected range: Minimum allowed expiry: 2024-09-25 16:20:14.229894131 UTC, Maximum allowed expiry: 2024-09-25 16:25:44.229894131 UTC, Provided expiry: 2024-09-25 16:20:00 UTC ---
**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\ **Post date:** [September 30, 2024, 11:22am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/28 "2024-09-30T11:22:32Z")
Thanks for the feedback. The SDK team has reverted a feature and released a new version of `agent-js` ( **v2.1.2** ). Could you give it a try and let them know if it helps? ---
**Author:** ![Alishan](https://avatars.discourse-cdn.com/v4/letter/a/d6d6ee/32.png) [@Alishan](https://forum.dfinity.org/u/Alishan)\ **Post date:** [September 30, 2024, 11:33am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/29 "2024-09-30T11:33:49Z")
i am already using older version of becasue my project is 1 year older “@dfinity/agent”: “^0.18.1”, “@dfinity/auth-client”: “^0.18.1”, “@dfinity/candid”: “^0.18.1”, “@dfinity/identity”: “^0.18.1”, “@dfinity/ledger-icp”: “^2.0.0”, “@dfinity/nns-proto”: “^1.0.0”, “@dfinity/principal”: “^0.18.1”, “@dfinity/utils”: “^1.1.0”, ---
**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\ **Post date:** [September 30, 2024, 11:44am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/30 "2024-09-30T11:44:11Z")
Oh I see. I’ll forward your feedback to the team. ---
**Author:** ![TusharGuptaMm](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/tusharguptamm/32/11944_2.png) [@TusharGuptaMm](https://forum.dfinity.org/u/TusharGuptaMm)\ **Post date:** [October 1, 2024, 7:47am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/31 "2024-10-01T07:47:39Z")
It doesn’t seem like the issue is related to agent-js; this looks more like a backend problem. In our case, inter-canister calls are also failing, including one-way calls that are ending up unsuccessful. ---
**Author:** ![jamesbeadle](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jamesbeadle/32/10110_2.png) [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)\ **Post date:** [October 1, 2024, 5:56pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/32 "2024-10-01T17:56:49Z")
So I redeployed OpenFPL to new canisters, surely they are on a new subnet than the old one I deployed to a year ago, I get the same error from a new canister: ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/f/3/f31c21c625c6f2ce9eb75b6d80c2e837ed2c2d60.png) ---
**Author:** ![dfx-json](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dfx-json/32/4784_2.png) [@dfx-json](https://forum.dfinity.org/u/dfx-json)\ **Post date:** [October 1, 2024, 7:17pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/33 "2024-10-01T19:17:19Z")
Hi James. We think this issue is a compound of subnet load issues, along with the JavaScript agent’s attempt to reconcile differences between replica time and system time. Since it doesn’t appear that subnet load was the factor in your case, I suspect it may be the agent version. Can you confirm if you are using version 2.1.1? If so please update to 2.1.2 or downgrade to 2.1.0 To be transparent, we are working on a protocol-level solution that will allow agents to synchronize clocks with the subnet they are calling into in a trustable manner. These ingress expiry errors will go away once we have that up and running. We should have something in beta in a couple weeks. Super sorry for the trouble and inconvenience. We probably could have solved it with an unsafe hack, but that’s not what we’re about. I hope you and others can accept that we are putting more time and effort into this so that we ship something safe and reliable. Can I gift you a Cycles coupon (or something else) for your trouble? ---
**Author:** ![jamesbeadle](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jamesbeadle/32/10110_2.png) [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)\ **Post date:** [October 1, 2024, 7:54pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/34 "2024-10-01T19:54:00Z")
Gift me some cycles lol. I dunno how to get across the money involved in this for me. So I take the ICP I raised in the SNS, pay developers and associated other staff, we don’t have an app to promote. Everything has a lead time, so repeatedly, the string of delays I’ve experienced have cost me tens of thousands of pounds. It’s worse than that, because I truly decentralised my app, I have to go to my DAO token holders and ask for more funding, on the back of not delivering. Thanks for this, I’m sure they’ll be keen. I have a backlog of campaigns, content and other stuff that just sits here, all just wasting away. Like this week I wanted to bring out the women’s game, OpenWSL, a new women’s football neuron, I have people associated with the women’s England team ready to be involved, I have sponsorship deals ready to sign. The pressure of having people leave their web2 jobs to join the team, I had no idea this was some test project not ready for production. So no, I don’t want cycles, I want you to recognise you are potentially destroying my life, and for what? AI? 64 bit? Bob.fun blocking up the subnets, if only you’d supported OpenFPL the way you supported that ICP drain. ---
**Author:** ![dfx-json](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dfx-json/32/4784_2.png) [@dfx-json](https://forum.dfinity.org/u/dfx-json)\ **Post date:** [October 1, 2024, 9:47pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/35 "2024-10-01T21:47:00Z")
I get it, and I can only imagine what being under that kind of pressure is like. Every platform, every cloud provider has imperfections. ICP is a relatively small but growing project that is getting better every day. What cloud provider is going to have their engineers and executive leadership reach out to you directly? What cloud provider is going to prioritize your problems and tailor their roadmap to make sure you’re satisfied? Our commitment is to you and all of the developers building on ICP. So while I acknowledge you are experiencing some pain, I assure you that your forbearance will pay dividends in the end. And to get back to the issue — can you tell me your agent version so we can validate our hypothesis and run more tests internally? ---
**Author:** ![jamesbeadle](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jamesbeadle/32/10110_2.png) [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)\ **Post date:** [October 1, 2024, 10:22pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/36 "2024-10-01T22:22:08Z")
I was 2.1.1. Upgraded to agent 2.1.2 ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/0/d/0d8caeb5d4933cc496f3432733896dd577dea0a3.jpeg) Just making note of the date and time as I have data but i’ve had data before, hopefully this agent package update has fixed things for the time being. ---
**Author:** ![jamesbeadle](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jamesbeadle/32/10110_2.png) [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)\ **Post date:** [October 1, 2024, 10:45pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/37 "2024-10-01T22:45:48Z")
and 20 mins later I can no longer run that: ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/f/e/fed11e9a0fac6725a5502ca40739baad8435a35b.png) ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/1/5/15d0126471ec8916e813f07b1e25f7f4d52efd8c.png) ---
**Author:** ![jamesbeadle](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jamesbeadle/32/10110_2.png) [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)\ **Post date:** [October 1, 2024, 10:50pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/38 "2024-10-01T22:50:32Z")
And now running it is back to full ingress\_expiry error ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/3/3/33f8ca77ece3c3130764db6e9713498488b26dac.png) Under half hour. ---
**Author:** ![Alishan](https://avatars.discourse-cdn.com/v4/letter/a/d6d6ee/32.png) [@Alishan](https://forum.dfinity.org/u/Alishan)\ **Post date:** [October 2, 2024, 3:16am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/39 "2024-10-02T03:16:55Z")
I think its not related to version because my project is one year old and using older version of definity , it am facing this issue from last 3 weeks. I can do nothing. As l already told that my website is about articles, i am unable to create article if i put my time 1 mint ago then its work. ---
**Author:** ![BustyBeardo](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/bustybeardo/32/16506_2.png) [@BustyBeardo](https://forum.dfinity.org/u/BustyBeardo)\ **Post date:** [October 2, 2024, 10:15am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/40 "2024-10-02T10:15:49Z")
I’ve also been stuck on this issue for quite a few months now. I’ll take a cycles coupon and cheeky temporary work around if thats available. Thanks ---
**Author:** ![jamesbeadle](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jamesbeadle/32/10110_2.png) [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)\ **Post date:** [October 2, 2024, 11:00am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/41 "2024-10-02T11:00:19Z")
Advice I’ve received from community member is to: up the `compute_allocation` on the `canister_settings` to 1, will burn more cycles but probably fixes the issue. Will try when I figure out how [Previous page](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456.md?page=1) [Next page](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456.md?page=3)