# HTTPS outcall consensus errors when calling alchemy api

**URL:** <https://forum.dfinity.org/t/https-outcall-consensus-errors-when-calling-alchemy-api/33197>\
**Category:** Developers\
**Created:** [July 14, 2024, 1:33pm UTC](https://forum.dfinity.org/t/https-outcall-consensus-errors-when-calling-alchemy-api/33197 "2024-07-14T13:33:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [July 16, 2024, 7:54am UTC](https://forum.dfinity.org/t/https-outcall-consensus-errors-when-calling-alchemy-api/33197/4 "2024-07-16T07:54:28Z")

</div>

For a generic proxy solution for HTTP outcalls to support both IPv6 and idempotent answers, there are a couple of other references:

- Recently, @zensh shared a solution on this topic: [Idempotent Proxy Show: proxy HTTPS Outcalls to any Web2 service](https://forum.dfinity.org/t/idempotent-proxy-show-proxy-https-outcalls-to-any-web2-service/32754)

- Additionally, @massimoalbarello and @ilbert have proposed another solution parts of their IC Side Services activities: [Non replicated HTTPS outcalls](https://forum.dfinity.org/t/non-replicated-https-outcalls/26627)

* * *

PS: If not the case, it would be worth it if the foundation documented these solutions somewhere. It feels like I keep copying and pasting the same links in multiple threads.

---

_[View the full topic](https://forum.dfinity.org/t/https-outcall-consensus-errors-when-calling-alchemy-api/33197)._