# Ingress\_expiry not within expected range error
**URL:** https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456
**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:** 1
### Author:  [@Alishan](https://forum.dfinity.org/u/Alishan)
#### Post date: [September 23, 2024, 1:03pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/1 "2024-09-23T13:03:28Z")
hello there,
ingress\_expiry not within expected error when deploy frontend canister from server ,
to create static page i sent get data request to node api and node api call my backend canister to fetch data , some pages created and in some pages it throw an error ingress\_expiry not within expected range .
sometime its work well and sometime i face this error .
And on frontend my website is on article base when i try to publish the the article i face this error
2 week ago it was working well and now this error is happing.
and my time is also synced .i hope i will get authenticated solution from definity team.
---
### Author:  [@dantol29](https://forum.dfinity.org/u/dantol29)
#### Post date: [September 23, 2024, 1:55pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/2 "2024-09-23T13:55:35Z")
Had the same issue, but in Rust
---
### Author:  [@jennifertran](https://forum.dfinity.org/u/jennifertran)
#### Post date: [September 23, 2024, 10:52pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/3 "2024-09-23T22:52:42Z")
This is a potentially known issue. Can you and @dantol29 please let me know what subnet is the canister that you are on?
---
### Author:  [@Alishan](https://forum.dfinity.org/u/Alishan)
#### Post date: [September 24, 2024, 5:19am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/4 "2024-09-24T05:19:55Z")
> **[Subnet: 6pbhf-qzpdk-kuqbr-pklfa-5ehhf-jfjps-zsj6q-57nrl-kzhpd-mu7hc-vae](https://dashboard.internetcomputer.org/subnet/6pbhf-qzpdk-kuqbr-pklfa-5ehhf-jfjps-zsj6q-57nrl-kzhpd-mu7hc-vae)**
>
> Application subnet blockchain which hosts canister smart contracts and adds capacity to the Internet Computer.
---
### Author:  [@jennifertran](https://forum.dfinity.org/u/jennifertran)
#### Post date: [September 24, 2024, 5:27am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/5 "2024-09-24T05:27:54Z")
In the latest AgentJS release, you can set a specific `replicaTime`. Can you please try that and see if it helps per the other thread that we’re communicating in?
---
### Author:  [@Alishan](https://forum.dfinity.org/u/Alishan)
#### Post date: [September 24, 2024, 9:21am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/6 "2024-09-24T09:21:15Z")
i have update its version to latest and and i don;t know to to set its value replicaTime
i have set it like
const replicaTime = BigInt(Date.now()) \* BigInt(1\_000\_000); // Current time in nanoseconds
const agent = options.agent || HttpAgent.createSync({ …options.agentOptions ,replicaTime});
is it correct if not then reffer me how to do this. thanks
---
### Author:  [@dantol29](https://forum.dfinity.org/u/dantol29)
#### Post date: [September 24, 2024, 6:13pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/7 "2024-09-24T18:13:22Z")
BOB ledger - [https://dashboard.internetcomputer.org/canister/egjwt-lqaaa-aaaak-qi2aa-cai](https://dashboard.internetcomputer.org/canister/egjwt-lqaaa-aaaak-qi2aa-cai)
---
### Author:  [@dantol29](https://forum.dfinity.org/u/dantol29)
#### Post date: [September 25, 2024, 9:19am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/9 "2024-09-25T09:19:19Z")
Solution for those who use rust ic-agent library:
```auto
use time::{Duration, OffsetDateTime};
use ic_agent::Agent;
let now_utc = OffsetDateTime::now_utc();
let five_seconds = Duration::seconds(5);
let time = now_utc + five_seconds;
agent.query(&ledger.id, "get_transactions")
.expire_at(time)
.with_arg("your args").unwrap())
.call_without_verification().await
```
---
### Author:  [@Alishan](https://forum.dfinity.org/u/Alishan)
#### Post date: [September 25, 2024, 9:41am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/10 "2024-09-25T09:41:03Z")
how i can did this in next js creating agent please need help @jennifertran
when i send request to canister it show me error like ingress expiry screenshot i mentioned above
---
### Author:  [@dantol29](https://forum.dfinity.org/u/dantol29)
#### Post date: [September 25, 2024, 9:48am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/11 "2024-09-25T09:48:39Z")
[https://github.com/search?q=repo%3Adappblock%2Fnextjs-ic-starter%20agent&type=code](https://github.com/search?q=repo%3Adappblock%2Fnextjs-ic-starter%20agent&type=code)
---
### Author:  [@Ray04](https://forum.dfinity.org/u/Ray04)
#### Post date: [September 25, 2024, 10:06am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/12 "2024-09-25T10:06:16Z")
Had this weird error also in a project I worked on, had this when one of my team member has deployed the project on main net and while testing on main net, rust backend and react front end.
This was the issue, Some on the internet said that the system time might be wrong. Which we checked later on, and seemed to be correct.
Ultimately, we resolved the error by deploying again on main net in my laptop, and it worked perfectly. So, I’d suggest you to do that. Not another laptop, but prolly just deploying again on the main net.
---
### Author:  [@Alishan](https://forum.dfinity.org/u/Alishan)
#### Post date: [September 25, 2024, 11:10am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/13 "2024-09-25T11:10:18Z")
which canisiter i deploy now i send a request to backend canister which throw an error “ingress expiry” ,
is this reason can be i am send to many request to backend ? as i am creating build of nextjs and static pages and for each static page a create an actor and an send request to backend to get data? if anyone the reason than please let me know. thanks
---
### Author:  [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)
#### Post date: [September 25, 2024, 11:39am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/14 "2024-09-25T11:39:06Z")
Hi @jennifertran,
We have the same problem periodically, affecting network calls that require user to be authenticated.
Is there a fix?
Thanks,
James
---
### Author:  [@YAP](https://forum.dfinity.org/u/YAP)
#### Post date: [September 25, 2024, 4:48pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/15 "2024-09-25T16:48:35Z")
Dear Alishan and James
The root of the problem you encountered is the fact that a client’s time can be ahead of the replica’s time which receives the message. Moreover the time certified by the subnet’s nodes can differ from both those times as well. We are aware of the problem and we’re discussing different options to improve the situation. We should be able to communicate a more concrete plan soon.
---
### Author:  [@Alishan](https://forum.dfinity.org/u/Alishan)
#### Post date: [September 25, 2024, 5:04pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/16 "2024-09-25T17:04:09Z")
Thanks @yvonneanne for your response. How i can make client time ahead ? Suggest be best solution because my project is live.
---
### Author:  [@TusharGuptaMm](https://forum.dfinity.org/u/TusharGuptaMm)
#### Post date: [September 25, 2024, 5:16pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/17 "2024-09-25T17:16:38Z")
We’ve been encountering this issue quite often as well whenever we do Update calls. We’re using Motoko for our canisters.
`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:  [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)
#### Post date: [September 25, 2024, 5:26pm UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/18 "2024-09-25T17:26:13Z")
Yeah a work around would be good for now
---
### Author:  [@jamesbeadle](https://forum.dfinity.org/u/jamesbeadle)
#### Post date: [September 26, 2024, 2:22am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/19 "2024-09-26T02:22:18Z")
So I deploy and it’s fine for a moment but then a few minutes later it is out of sync.
---
### Author:  [@Alishan](https://forum.dfinity.org/u/Alishan)
#### Post date: [September 26, 2024, 3:42am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/20 "2024-09-26T03:42:15Z")
I think it’s not from our end its from ICP. @YAP
---
### Author:  [@TusharGuptaMm](https://forum.dfinity.org/u/TusharGuptaMm)
#### Post date: [September 26, 2024, 5:30am UTC](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456/21 "2024-09-26T05:30:12Z")
This issue might be subnet-specific, though it’s just a guess—it could be related to the V3 release aimed at [reducing end-to-end latencies](https://forum.dfinity.org/t/reducing-end-to-end-latencies-on-the-internet-computer/34383) ?
[Next page](https://forum.dfinity.org/t/ingress-expiry-not-within-expected-range-error/35456.md?page=2)