starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

IPv6-only does not work in some environments #2149

New issue

Closed

opened 2026-02-28 02:44:40 -05:00 by deekerman · 10 comments

deekerman commented

2026-02-28 02:44:40 -05:00

Owner

Originally created by @solick on GitHub (Apr 29, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

Currently it is not possible to monitor server which has only an ipv6 address. I tested with a virtual machine which has only an ipv6 address with ping monitoring and the server is down as inactive. Tested the same machine with uptimerobot and the server is shown as up and running.

Because Ipv6 is the future and Ipv4 is legacy, uptime-duma should support ipv6 monitoring.

✔️ Solution

Either enable ping monitoring to test v4 and v6 or add a new ping6 monitoring.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @solick on GitHub (Apr 29, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description Currently it is not possible to monitor server which has only an ipv6 address. I tested with a virtual machine which has only an ipv6 address with ping monitoring and the server is down as inactive. Tested the same machine with uptimerobot and the server is shown as up and running. Because Ipv6 is the future and Ipv4 is legacy, uptime-duma should support ipv6 monitoring. ### ✔️ Solution Either enable ping monitoring to test v4 and v6 or add a new ping6 monitoring. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:44:40 -05:00

closed this issue
added the
feature-request

A:core

blocked-upstream
labels

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@n-thumann commented on GitHub (Jul 5, 2023):

Is this still the case? I am currently running Uptime Kuma on a IPv6-only server and monitoring ipv6.google.com (doesn't have an A record) with no issues ✌️

@n-thumann commented on GitHub (Jul 5, 2023): Is this still the case? I am currently running Uptime Kuma on a IPv6-only server and monitoring `ipv6.google.com` (doesn't have an A record) with no issues :v:

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@solick commented on GitHub (Jul 5, 2023):

It was only the case using the docker variant. I installed uptime kuma now plain on a vm and now it works.

@solick commented on GitHub (Jul 5, 2023): It was only the case using the docker variant. I installed uptime kuma now plain on a vm and now it works.

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@benniju commented on GitHub (May 27, 2024):

Hi, I can only run Uptime Kuma in docker, because I use Home Assistant OS. Would it be possible to add IPv6 support to the Docker images?

@benniju commented on GitHub (May 27, 2024): Hi, I can only run Uptime Kuma in docker, because I use Home Assistant OS. Would it be possible to add IPv6 support to the Docker images?

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@CommanderStorm commented on GitHub (May 27, 2024):

We support ipv6.
Without additional details about your setup it is basically impossible to help you.
=> What are you trying to monitor?

Why you are likely wondering if we support this is because we don't have happy eyeballs v2 due to the node version we packaged.
If you are asking to select which stack you are using: this is currently not possible in nodejs (see #1242)

We have upgraded nodejs for uptime-kuma V2. You can see #4500 for the bugs which will need to be fixed before we can publish the beta.

@CommanderStorm commented on GitHub (May 27, 2024): We support ipv6. Without additional details about your setup it is basically impossible to help you. => What are you trying to monitor? Why you are likely wondering if we support this is because we don't have happy eyeballs v2 due to the node version we packaged. If you are asking to select which stack you are using: this is currently not possible in nodejs (see #1242) We have upgraded nodejs for uptime-kuma V2. You can see #4500 for the bugs which will need to be fixed before we can publish the beta.

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@benniju commented on GitHub (May 27, 2024):

I am running v1.23.13 in Home Assistant OS using the following addon: https://github.com/hassio-addons/addon-uptime-kuma
I have tried adding a ping monitor for an Hostname which only has an AAAA (IPv6) record and no A (IPv4) record and IP address.
When I save the monitor I get the message that it is down with the error ping: connect: Address not available. When I try to add the IP Address itself with braces, I can't even save the monitor.

This is the output when I try to use ping in the docker container using docker exec:

root@a0d7b954-uptime-kuma:/opt$ ping google.de
PING google.de (142.250.186.35) 56(84) bytes of data.
64 bytes from fra24s04-in-f3.1e100.net (142.250.186.35): icmp_seq=1 ttl=114 time=19.9 ms
^C
--- google.de ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 19.858/19.858/19.858/0.000 ms
root@a0d7b954-uptime-kuma:/opt$ ping -6 google.de
ping: connect: Address not available
root@a0d7b954-uptime-kuma:/opt$ ping6 google.de
ping6: connect: Address not available

So it seems that the container does not have any IPv6 support at all. This is not the case for other Home Assistant Containers.
Although I have noticed that the hass docker image is not based on this docker image, so maybe I should open the issue there?

@benniju commented on GitHub (May 27, 2024): I am running v1.23.13 in Home Assistant OS using the following addon: https://github.com/hassio-addons/addon-uptime-kuma I have tried adding a ping monitor for an Hostname which only has an AAAA (IPv6) record and no A (IPv4) record and IP address. When I save the monitor I get the message that it is down with the error `ping: connect: Address not available`. When I try to add the IP Address itself with braces, I can't even save the monitor. This is the output when I try to use ping in the docker container using docker exec: ``` root@a0d7b954-uptime-kuma:/opt$ ping google.de PING google.de (142.250.186.35) 56(84) bytes of data. 64 bytes from fra24s04-in-f3.1e100.net (142.250.186.35): icmp_seq=1 ttl=114 time=19.9 ms ^C --- google.de ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 19.858/19.858/19.858/0.000 ms root@a0d7b954-uptime-kuma:/opt$ ping -6 google.de ping: connect: Address not available root@a0d7b954-uptime-kuma:/opt$ ping6 google.de ping6: connect: Address not available ``` So it seems that the container does not have any IPv6 support at all. This is not the case for other Home Assistant Containers. Although I have noticed that the hass docker image is not based on this docker image, so maybe I should open the issue there?

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@CommanderStorm commented on GitHub (May 27, 2024):

Is the URL publicly routable? If yes, could you provide the URL you are testing against?

Is this reproducible on uptime.kuma.pet ?
(I am trying to rule out bad docker networking, which is somewhat of a common occurrence)

Alternatively (idk how to do that via your deployment variant, we don't maintain that and I don't use it) you can try our troubleshooting steps here and see if it is a docker network is configured correctly:
https://github.com/louislam/uptime-kuma/wiki/Troubleshooting

I don't know what is the problem with ipv6 in the ping monitor. Likely the allowed regex needs adjusting.
The pattern is currently quite complicated

@CommanderStorm commented on GitHub (May 27, 2024): Is the URL publicly routable? If yes, could you provide the URL you are testing against? Is this reproducible on uptime.kuma.pet ? (I am trying to rule out bad docker networking, which is somewhat of a common occurrence) Alternatively (idk how to do that via your deployment variant, we don't maintain that and I don't use it) you can try our troubleshooting steps here and see if it is a docker network is configured correctly: https://github.com/louislam/uptime-kuma/wiki/Troubleshooting I don't know what is the problem with ipv6 in the ping monitor. Likely the allowed regex needs adjusting. The pattern is currently quite complicated

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@CommanderStorm commented on GitHub (May 27, 2024):

The current regex is here:

github.com/louislam/uptime-kuma@11007823e7/src/util-frontend.js (L111-L126)

@CommanderStorm commented on GitHub (May 27, 2024): The current regex is here: https://github.com/louislam/uptime-kuma/blob/11007823e7207531da4d82cab0b774ee8ace6f57/src/util-frontend.js#L111-L126

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@benniju commented on GitHub (May 27, 2024):

Is the URL publicly routable? If yes, could you provide the URL you are testing against?

Yes, but I do not want to publish the URL. But the same problem also occurs when adding ipv6.google.com.

Is this reproducible on uptime.kuma.pet ? (I am trying to rule out bad docker networking, which is somewhat of a common occurrence)

Yes, the ping also does not work there with the error connect: Network is unreachable

Alternatively (idk how to do that via your deployment variant, we don't maintain that and I don't use it) you can try our troubleshooting steps here and see if it is a docker network is configured correctly: https://github.com/louislam/uptime-kuma/wiki/Troubleshooting

root@a0d7b954-uptime-kuma:/opt$ curl https://ipv6.google.com
curl: (7) Failed to connect to ipv6.google.com port 443 after 4 ms: Couldn't connect to server
root@a0d7b954-uptime-kuma:/opt$ ping ipv6.google.com
ping: connect: Address not available

So as I also noted before it does seem that the container does not have any IPv6 Support at all, so it is likely a docker network problem. Should I open an issue in the addons repo instead? I find it interesting though, that the IPv6 ping also fails on the demo, but with a different error.

@benniju commented on GitHub (May 27, 2024): > Is the URL publicly routable? If yes, could you provide the URL you are testing against? Yes, but I do not want to publish the URL. But the same problem also occurs when adding ipv6.google.com. > Is this reproducible on uptime.kuma.pet ? (I am trying to rule out bad docker networking, which is somewhat of a common occurrence) Yes, the ping also does not work there with the error `connect: Network is unreachable` > Alternatively (idk how to do that via your deployment variant, we don't maintain that and I don't use it) you can try our troubleshooting steps here and see if it is a docker network is configured correctly: https://github.com/louislam/uptime-kuma/wiki/Troubleshooting ``` root@a0d7b954-uptime-kuma:/opt$ curl https://ipv6.google.com curl: (7) Failed to connect to ipv6.google.com port 443 after 4 ms: Couldn't connect to server root@a0d7b954-uptime-kuma:/opt$ ping ipv6.google.com ping: connect: Address not available ``` So as I also noted before it does seem that the container does not have any IPv6 Support at all, so it is likely a docker network problem. Should I open an issue in the addons repo instead? I find it interesting though, that the IPv6 ping also fails on the demo, but with a different error.

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@benniju commented on GitHub (May 27, 2024):

I have now enabled host networking in a customised version of the container, and now the ping works fine.
This is not really recommended though and lowers the "security rating" of the addon and you also can't simply modify the port of the webserver easily then. It probably seems to be a general issue with IPv6 networking in Home Assistant then and not a issue in Uptime Kuma.

@benniju commented on GitHub (May 27, 2024): I have now enabled host networking in a customised version of the container, and now the ping works fine. This is not really recommended though and lowers the "security rating" of the addon and you also can't simply modify the port of the webserver easily then. It probably seems to be a general issue with IPv6 networking in Home Assistant then and not a issue in Uptime Kuma.

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@CommanderStorm commented on GitHub (May 28, 2024):

ipv6 networking in docker (docs at https://docs.docker.com/config/daemon/ipv6/) needs to be enabled.
By default only IPv4 is available.

For home assistant this is tracked/discussed here:
https://github.com/home-assistant/supervisor/issues/2133

Closing as nothing we can do. Upstream support needs to be enabled manually.
If there is something that we are missing, please comment and we can reopen the issue ^^

@CommanderStorm commented on GitHub (May 28, 2024): ipv6 networking in docker (docs at https://docs.docker.com/config/daemon/ipv6/) needs to be enabled. By default only IPv4 is available. For home assistant this is tracked/discussed here: https://github.com/home-assistant/supervisor/issues/2133 Closing as nothing we can do. Upstream support needs to be enabled manually. If there is something that we are missing, please comment and we can reopen the issue ^^