# New HTTP Gateway error page: How to detailed error

**URL:** <https://forum.dfinity.org/t/new-http-gateway-error-page-how-to-detailed-error/53296>\
**Category:** Developers\
**Created:** [July 15, 2025, 7:42pm UTC](https://forum.dfinity.org/t/new-http-gateway-error-page-how-to-detailed-error/53296 "2025-07-15T19:42:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gekctek](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gekctek/32/6863_2.png) [@Gekctek](https://forum.dfinity.org/u/Gekctek)\
**Post date:** [July 15, 2025, 7:42pm UTC](https://forum.dfinity.org/t/new-http-gateway-error-page-how-to-detailed-error/53296/1 "2025-07-15T19:42:29Z")

</div>

Locally (0.28.0+) and on mainnet, I am no longer able to see the specific error for Response Verification issues  
Before it was simple text like ‘Invalid root tree hash’ but now is just a generic message

 ![image](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/3X/4/1/41a8e3d79caab8750b1f9f087d185d5e9b37f837.png)  
Any way of getting more details?

---

<div class="post-metadata">

**Author:** ![rbirkner](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@rbirkner](https://forum.dfinity.org/u/rbirkner)\
**Post date:** [July 16, 2025, 10:32am UTC](https://forum.dfinity.org/t/new-http-gateway-error-page-how-to-detailed-error/53296/2 "2025-07-16T10:32:20Z")

</div>

Hey @Gekctek,

Indeed the HTTP gateways don’t expose details anymore as we deemed them not actionable for “end users”. You can still access the full details by directly using the `ic-response-verification` crate. @NathanosDev has a [sample script here](https://github.com/nathanosdev/dfx-playground/tree/main/ic-certificate-explorer) and we will make sure to prepare something more “official” and with the latest releases of the crates in the coming weeks.

When you are using that `ic-certificate-explorer`, make sure to fix the `Cargo.toml` by replacing [these lines](https://github.com/nathanosdev/dfx-playground/blob/main/ic-certificate-explorer/Cargo.toml#L17-L18) with:

```auto
ic-response-verification = { version = "2.0.1", features = ["debug"] }
ic-http-certification = { version = "2.0.1" }

```

Then, you can adapt [the following lines](https://github.com/nathanosdev/dfx-playground/blob/main/ic-certificate-explorer/src/main.rs#L78-L82) to make a call against your canister. For mainnet, use `https://icp-api.io` and for local development `localhost` with the right port. Also, make sure to request the right verification version [here](https://github.com/nathanosdev/dfx-playground/blob/main/ic-certificate-explorer/src/main.rs#L95) and [here](https://github.com/nathanosdev/dfx-playground/blob/main/ic-certificate-explorer/src/main.rs#L130).

I hope this unblocks you for now. If you need any help, let us know!