WOL Relay Container

A minimal HTTP relay container that sends an authenticated Wake-on-LAN magic packet when it receives a POST, letting tools such as Home Assistant wake devices…

  • Home Automation
  • Network Services
  • Tools & Utilities
A minimal HTTP relay container that sends an authenticated Wake-on-LAN magic packet when it receives a POST, letting tools such as Home Assistant wake devices without a web UI or stored data.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

47/100 Fair

Maintained
82last commit 24 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed 13 days ago

GitHub stars
0
Open issues
2
Last commit
2026-10-28
Latest release
v1.0.6
License
MIT
Activity
rising

Checked 23 days ago - source: GitHub (Tom-Joad/wol-relay-container)

Resources & Compatibility

Requirements not published yet.

Checked 46 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Configuration at first install Supply the shared secret, target MAC address, broadcast address, and ports as environment variables at runtime; the repository ships with no real values. Run the container with host networking on a Docker host that sits in the same network segment as the machine to be woken, so the UDP broadcast packet reaches the target without extra bridge or macvlan configuration. source
  • Host networking and environment setup Run with host networking on a host in the same Layer 2 segment as the target, then set the shared secret, target MAC, broadcast address, and ports via environment variables. source
  • Network and environment setup Run the container with network_mode: host so it sits in the same layer-2 (L2) segment as the machine you want to wake; this lets the UDP broadcast reach the target without extra macvlan or bridge networking. Supply the shared secret, target MAC address, broadcast address, and ports as environment variables — the repository ships no real values. source

Fetched 43 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What kind of request wakes a device?

It sends a Wake-on-LAN magic packet when it receives an authenticated POST request.

Can it be used with something other than Home Assistant?

It is built as a Home Assistant trigger target, but it is plain HTTP and works with anything that can issue a POST.

What Docker networking setup is required?

The container should run with network_mode: host, and the Docker host should sit in the same network segment as the target device.

Does it store configuration or activity data?

No, it has no web UI and no stored data, and activity is only in the container log.

Answers sourced from github.com

Community

Collected 44 days ago - public community threads