starred/uptime-kuma

Fork 0

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

Provide an optional Wake On LAN (WOL) feature, per entry #478

New issue

Open

opened 2026-02-28 01:47:50 -05:00 by deekerman · 12 comments

deekerman commented

2026-02-28 01:47:50 -05:00

Owner

Originally created by @kdorff on GitHub (Oct 26, 2021).

Describe the solution you'd like
It would be nice is there was an option, per entry, to send a Wake On LAN (WOL) packet when a service was observed as down. And likely an IP address to send the WOL packet to. Perhaps a configuration "don't send more often than..."? I'm not sure what options are generally provided around sending WOL.

Describe alternatives you've considered
Noticing the server is down (being notified by Kuma) and turning it back on manually.

Originally created by @kdorff on GitHub (Oct 26, 2021). **Describe the solution you'd like** It would be nice is there was an option, per entry, to send a Wake On LAN (WOL) packet when a service was observed as down. And likely an IP address to send the WOL packet to. Perhaps a configuration "don't send more often than..."? I'm not sure what options are generally provided around sending WOL. **Describe alternatives you've considered** Noticing the server is down (being notified by Kuma) and turning it back on manually.

deekerman added the

feature-request

A:notifications

labels

2026-02-28 01:47:50 -05:00

deekerman commented

2026-02-28 01:47:54 -05:00

Author

Owner

@deefdragon commented on GitHub (Oct 27, 2021):

This sounds like it could be implemented by having a notification type of Wake On Lan that sends the packet.

@deefdragon commented on GitHub (Oct 27, 2021): This sounds like it could be implemented by having a notification type of Wake On Lan that sends the packet.

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@kdorff commented on GitHub (Oct 27, 2021):

This sounds like it could be implemented by having a notification type of Wake On Lan that sends the packet.

This sounds like a perfect, easy to understand solution.

@kdorff commented on GitHub (Oct 27, 2021): > This sounds like it could be implemented by having a notification type of Wake On Lan that sends the packet. This sounds like a perfect, easy to understand solution.

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@e-p-s commented on GitHub (Aug 13, 2022):

@e-p-s commented on GitHub (Aug 13, 2022): +1

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@Computroniks commented on GitHub (Aug 13, 2022):

@kdorff Could you provide some information about a possible usecase for this feature. Would it be used to "Wake up" a server that has entered the low power state and has been detected down? I am not really sure of its usefulness as if a server is down, it is most likely because of a network error which wouldn't be helped by a WOL packet or the server has crashed (not sure if WOL would work here).

@Computroniks commented on GitHub (Aug 13, 2022): @kdorff Could you provide some information about a possible usecase for this feature. Would it be used to "Wake up" a server that has entered the low power state and has been detected down? I am not really sure of its usefulness as if a server is down, it is most likely because of a network error which wouldn't be helped by a WOL packet or the server has crashed (not sure if WOL would work here).

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@Meulator commented on GitHub (Sep 29, 2022):

@Computroniks I dont think it would be used with servers, but maybe with computers ; i think it would be useful, for people doing RDP to their fixed box from home for instance, having the opportunity to start it in case of power outage for instance.

@Meulator commented on GitHub (Sep 29, 2022): @Computroniks I dont think it would be used with servers, but maybe with computers ; i think it would be useful, for people doing RDP to their fixed box from home for instance, having the opportunity to start it in case of power outage for instance.

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@arunoruto commented on GitHub (Sep 29, 2022):

@Meulator usually you can also set the PC to turn on right after the power is back.

This usually works if the environment is not prone to frequent subsequent outages in a row, e.g. the weather is bad and cows are flying through the skies. In such situations leaving the machine off would be better, and when the problem has been solved you could turn it on using WOL.

@arunoruto commented on GitHub (Sep 29, 2022): @Meulator usually you can also set the PC to turn on right after the power is back. This usually works if the environment is not prone to frequent subsequent outages in a row, e.g. the weather is bad and cows are flying through the skies. In such situations leaving the machine off would be better, and when the problem has been solved you could turn it on using WOL.

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@Meulator commented on GitHub (Sep 29, 2022):

@SoulEater45 yes, you're right, but we are in a very specific configuration ; putting too much PC on restart when power back might create another outage due to the surge on power-on ; anyways, we found a way to do so with a single php webpage so we're good :)

@Meulator commented on GitHub (Sep 29, 2022): @SoulEater45 yes, you're right, but we are in a very specific configuration ; putting too much PC on restart when power back might create another outage due to the surge on power-on ; anyways, we found a way to do so with a single php webpage so we're good :)

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@arunoruto commented on GitHub (Sep 29, 2022):

@Meulator that is true too, haven't thought about it!
As for the WOL problem, I have also found a nice substitute called upsnap. It looks nice and has a network scan feature (which would be a nice addition to kuma, to make machine monitoring a bit easier/more convenient).

@arunoruto commented on GitHub (Sep 29, 2022): @Meulator that is true too, haven't thought about it! As for the WOL problem, I have also found a nice substitute called [upsnap](https://github.com/seriousm4x/UpSnap). It looks nice and has a network scan feature (which would be a nice addition to kuma, to make machine monitoring a bit easier/more convenient).

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@tomeurp commented on GitHub (Jul 19, 2023):

This would be very useful indeed. I run a sql server at my business which is shut down every night to save on power consumption. This is fine because it is normally only needed during business hours. Ocasionally, however, I need to access the server via RDP outside of business hours and it would be pretty neat to be able to just wake the server from the wonderful interface of uptime kuma. I actually acomplish this via a user-defined-script in my synology nas, but it is a bit cumbersome and not user friendly at all to have to log into dsm open the control panel and run the script.
Hope this gets implemented soon.
Thanks.

@tomeurp commented on GitHub (Jul 19, 2023): This would be very useful indeed. I run a sql server at my business which is shut down every night to save on power consumption. This is fine because it is normally only needed during business hours. Ocasionally, however, I need to access the server via RDP outside of business hours and it would be pretty neat to be able to just wake the server from the wonderful interface of uptime kuma. I actually acomplish this via a user-defined-script in my synology nas, but it is a bit cumbersome and not user friendly at all to have to log into dsm open the control panel and run the script. Hope this gets implemented soon. Thanks.

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@Head commented on GitHub (Feb 23, 2025):

Usecase: Running a local DNS Server. DNS Check fails: WoL the backup server (which is powered off to save energy).

@Head commented on GitHub (Feb 23, 2025): Usecase: Running a local DNS Server. DNS Check fails: WoL the backup server (which is powered off to save energy).

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@ke1pl commented on GitHub (Jul 11, 2025):

@Meulator that is true too, haven't thought about it! As for the WOL problem, I have also found a nice substitute called upsnap. It looks nice and has a network scan feature (which would be a nice addition to kuma, to make machine monitoring a bit easier/more convenient).

I have the same problem, the same solution and the same feature request that was described in this comment :)

@ke1pl commented on GitHub (Jul 11, 2025): > [@Meulator](https://github.com/Meulator) that is true too, haven't thought about it! As for the WOL problem, I have also found a nice substitute called [upsnap](https://github.com/seriousm4x/UpSnap). It looks nice and has a network scan feature (which would be a nice addition to kuma, to make machine monitoring a bit easier/more convenient). I have the same problem, the same solution and the same feature request that was described in this comment :)

deekerman commented

2026-02-28 01:47:55 -05:00

Author

Owner

@jztreso commented on GitHub (Jul 22, 2025):

Could you provide some information about a possible usecase for this feature.
I for example run a home lab with multiple PCs. Some of them support powerup at power back, but some don't.
If my main NAS (which is running uptime kuma) boots up from a power outage, it can assist with booting up my other machines if it detects they aren't pinging back.
It could also be used to boot up VMs or machines at specific times a day.
If you seat the ping interval to just once per day, say at 8am, you could use it to boot up one, or a cluster at that time.

@jztreso commented on GitHub (Jul 22, 2025): **Could you provide some information about a possible usecase for this feature.** I for example run a home lab with multiple PCs. Some of them support powerup at power back, but some don't. If my main NAS (which is running uptime kuma) boots up from a power outage, it can assist with booting up my other machines if it detects they aren't pinging back. It could also be used to boot up VMs or machines at specific times a day. If you seat the ping interval to just once per day, say at 8am, you could use it to boot up one, or a cluster at that time.