[GH-ISSUE #841] Send Wake-on-LAN magic packet option for Streams host access in order to wake up target server #714

Open
opened 2026-02-26 06:34:06 +03:00 by kerem · 9 comments
Owner

Originally created by @fiveangle on GitHub (Jan 24, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/841

In the Streams interface, NPM allows access at an incoming port to be proxied to an internal host:port. For hosts that may be in an ACPI suspended state, the stream access will fail. An ideal solution would be to implement a "Send Wake-on-LAN packet" toggle within the Stream setup dialog. As NPM would only be able to know what the MAC address for the target device is if the target IP is active when setting up the Stream, NPM would either have to only allow enabling the toggle if the IP address is active during setup, or optionally, could include a field for the user to enter the MAC address directly. Either way (or both) would be plenty sufficient I think.

Variations that could be implemented are a set additional delay before responding to the client with the stream connection (which may allow a bit of time for the software on the WOL machine to fully resume operation, but I don't know if this will even be necessary - perhaps not).

This feature would allow those of us with media servers to script these systems to go to sleep when there are no active clients connected for a certain period, then resume operation upon client access.

I think this new feature would be a huge hit for Plex and other media server users ❤️

Regardless, I'm loving what you've put together here with NPM !

Originally created by @fiveangle on GitHub (Jan 24, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/841 In the Streams interface, NPM allows access at an incoming port to be proxied to an internal host:port. For hosts that may be in an ACPI suspended state, the stream access will fail. An ideal solution would be to implement a "Send Wake-on-LAN packet" toggle within the Stream setup dialog. As NPM would only be able to know what the MAC address for the target device is if the target IP is active when setting up the Stream, NPM would either have to only allow enabling the toggle if the IP address is active during setup, or optionally, could include a field for the user to enter the MAC address directly. Either way (or both) would be plenty sufficient I think. Variations that could be implemented are a set additional delay before responding to the client with the stream connection (which may allow a bit of time for the software on the WOL machine to fully resume operation, but I don't know if this will even be necessary - perhaps not). This feature would allow those of us with media servers to script these systems to go to sleep when there are no active clients connected for a certain period, then resume operation upon client access. I think this new feature would be a huge hit for Plex and other media server users ❤️ Regardless, I'm loving what you've put together here with NPM !
Author
Owner

@sebastienvermeille commented on GitHub (Nov 7, 2022):

Would be great indeed.

I have found this for now but this is a fork of nginx if I understood correctly: https://serverfault.com/a/948285

Maybe it give some help

<!-- gh-comment-id:1305207420 --> @sebastienvermeille commented on GitHub (Nov 7, 2022): Would be great indeed. I have found this for now but this is a fork of nginx if I understood correctly: https://serverfault.com/a/948285 Maybe it give some help
Author
Owner

@github-actions[bot] commented on GitHub (Mar 20, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2008552409 --> @github-actions[bot] commented on GitHub (Mar 20, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@tristan-k commented on GitHub (Mar 24, 2024):

Bump

<!-- gh-comment-id:2016783921 --> @tristan-k commented on GitHub (Mar 24, 2024): Bump
Author
Owner

@github-actions[bot] commented on GitHub (Dec 15, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2543413873 --> @github-actions[bot] commented on GitHub (Dec 15, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@tristan-k commented on GitHub (Dec 15, 2024):

Bump

<!-- gh-comment-id:2543835494 --> @tristan-k commented on GitHub (Dec 15, 2024): Bump
Author
Owner

@HunterAhlquist commented on GitHub (Feb 7, 2025):

Bump

<!-- gh-comment-id:2643934785 --> @HunterAhlquist commented on GitHub (Feb 7, 2025): Bump
Author
Owner

@fiveangle commented on GitHub (Feb 9, 2025):

Thank you army of fellow NPM fans for keeping this from getting auto-closed ♥️

Maybe when PG&E gets their next round of price hikes approved, I may spend a weekend to figure this out myself 😉

<!-- gh-comment-id:2646645537 --> @fiveangle commented on GitHub (Feb 9, 2025): Thank you army of fellow NPM fans for keeping this from getting auto-closed ♥️ Maybe when PG&E gets their next round of price hikes approved, I may spend a weekend to figure this out myself 😉
Author
Owner

@github-actions[bot] commented on GitHub (Nov 11, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:3514689383 --> @github-actions[bot] commented on GitHub (Nov 11, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@tristan-k commented on GitHub (Nov 11, 2025):

Bump.

<!-- gh-comment-id:3516267244 --> @tristan-k commented on GitHub (Nov 11, 2025): Bump.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#714
No description provided.