# Bind to ipv6 address

**URL:** <https://community.questdb.com/t/bind-to-ipv6-address/208>\
**Category:** Community\
**Created:** [October 22, 2024, 8:23pm UTC](https://community.questdb.com/t/bind-to-ipv6-address/208 "2024-10-22T20:23:33Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Armin\_Diehl](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/armin_diehl/32/113_2.png) [@Armin\_Diehl](https://community.questdb.com/u/Armin_Diehl)\
**Post date:** [October 22, 2024, 8:23pm UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/1 "2024-10-22T20:23:33Z")

</div>

is there a way to bind to an ipv6 address as well, have not found it in the documentation,  
http.bind.to  
refers to ipv4 only  
?

---

<div class="post-metadata">

**Author:** ![AndreKR](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/andrekr/32/116_2.png) [@AndreKR](https://community.questdb.com/u/AndreKR)\
**Post date:** [October 24, 2024, 4:53pm UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/2 "2024-10-24T16:53:37Z")

</div>

Yes, or at least make it listen on _all_ adresses, I couldn’t even get that to work.

For HTTP I currently let the reverse proxy translate, but for some reason Grafana uses the Postgres wire protocol so reverse proxy is not an option.

---

<div class="post-metadata">

**Author:** ![Armin\_Diehl](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/armin_diehl/32/113_2.png) [@Armin\_Diehl](https://community.questdb.com/u/Armin_Diehl)\
**Post date:** [October 24, 2024, 6:47pm UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/3 "2024-10-24T18:47:19Z")

</div>

Thanks for the answer, i dont care about Grafana as it is running on the same host. I simply want to have HTTP available on IPV6.  
If i understand your answer correctly, there is no native way to make HTTP listen on IPV6.

---

<div class="post-metadata">

**Author:** ![AndreKR](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/andrekr/32/116_2.png) [@AndreKR](https://community.questdb.com/u/AndreKR)\
**Post date:** [October 24, 2024, 8:31pm UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/4 "2024-10-24T20:31:52Z")

</div>

> [@Armin\_Diehl](#):
>
> If i understand your answer correctly, there is no native way to make HTTP listen on IPV6.

I don’t know, I was just voicing that I have the same or a very similar issue.

That said, no way at all to have the HTTP server listen on IPv6 would be a bit strange in 2024.

---

<div class="post-metadata">

**Author:** ![Rafael\_Karczevski](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/rafael_karczevski/32/380_2.png) [@Rafael\_Karczevski](https://community.questdb.com/u/Rafael_Karczevski)\
**Post date:** [April 15, 2025, 9:11am UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/5 "2025-04-15T09:11:04Z")

</div>

You resolved this? I trying deploy this on railway, then i need bind in ipv6 interface

---

<div class="post-metadata">

**Author:** ![nwoolmer](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/nwoolmer/32/24_2.png) [@nwoolmer](https://community.questdb.com/u/nwoolmer)\
**Post date:** [April 15, 2025, 10:12am UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/6 "2025-04-15T10:12:16Z")

</div>

No change yet, but I have re-raised it.

---

<div class="post-metadata">

**Author:** ![Rafael\_Karczevski](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/rafael_karczevski/32/380_2.png) [@Rafael\_Karczevski](https://community.questdb.com/u/Rafael_Karczevski)\
**Post date:** [April 17, 2025, 8:48am UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/7 "2025-04-17T08:48:17Z")

</div>

Is it still not possible to bind to IPv6?

---

<div class="post-metadata">

**Author:** ![nwoolmer](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/nwoolmer/32/24_2.png) [@nwoolmer](https://community.questdb.com/u/nwoolmer)\
**Post date:** [April 17, 2025, 8:48am UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/8 "2025-04-17T08:48:49Z")

</div>

In theory, it is currently possible, but it has not been tested to prove it, so I cannot say it is supported.

---

<div class="post-metadata">

**Author:** ![hevisko](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/hevisko/32/475_2.png) [@hevisko](https://community.questdb.com/u/hevisko)\
**Post date:** [August 5, 2025, 1:58pm UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/9 "2025-08-05T13:58:39Z")

</div>

Busy looking at deploying it in an IPv6 only network… so yeah, this is “fun” to not have support for IPv6 ;(

---

<div class="post-metadata">

**Author:** ![hevisko](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/hevisko/32/475_2.png) [@hevisko](https://community.questdb.com/u/hevisko)\
**Post date:** [November 16, 2025, 1:41pm UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/10 "2025-11-16T13:41:53Z")

</div>

Any plans to test this from questDB side?

---

<div class="post-metadata">

**Author:** ![nwoolmer](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/nwoolmer/32/24_2.png) [@nwoolmer](https://community.questdb.com/u/nwoolmer)\
**Post date:** [November 27, 2025, 10:16am UTC](https://community.questdb.com/t/bind-to-ipv6-address/208/11 "2025-11-27T10:16:05Z")

</div>

Hey @hevisko ,

Not before the end of the year. However, we do accept OSS contributions so if you think you/other users waiting are motivated or confident you can patch the server to support IPv6, we can support you.
