# Body: Specified ingress\_expiry not within expected range:

**URL:** <https://forum.dfinity.org/t/body-specified-ingress-expiry-not-within-expected-range/34015>\
**Category:** Developers\
**Tags:** Discussing\
**Created:** [August 8, 2024, 1:40pm UTC](https://forum.dfinity.org/t/body-specified-ingress-expiry-not-within-expected-range/34015 "2024-08-08T13:40:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\
**Post date:** [August 13, 2024, 9:41am UTC](https://forum.dfinity.org/t/body-specified-ingress-expiry-not-within-expected-range/34015/2 "2024-08-13T09:41:21Z")

</div>

Not the same error message but, it sounds vaguely similar to the SSG issue I encountered this weekend. @anon74414410 said there might be an inssue with `syncTime`:

> [@Agent-js does not work in Next.js SSG](https://forum.dfinity.org/t/agent-js-does-not-work-in-next-js-ssg/34090/4):
>
> I’d use createSync for SSG contexts as the simple fix, but the point is probably more to do with fetch or syncTime not working as intended. I have another reported issue with the syncTime flow, so I’m going to dive into this and get back to you

---

_[View the full topic](https://forum.dfinity.org/t/body-specified-ingress-expiry-not-within-expected-range/34015)._