[SUPPORT] SmartPhoneLover - Remote Wake/Sleep-On-LAN Server


Recommended Posts

rwsol-server.png

 

This docker template was created based on an already available docker image

 

Website: https://www.jeremyblum.com/2013/07/14/rpi-wol-server/

GitHub: https://github.com/ex0nuss/Remote-Wake-Sleep-On-LAN-Docker

GitHub (original): https://github.com/sciguy14/Remote-Wake-Sleep-On-LAN-Server
DockerHub: https://hub.docker.com/r/ex0nuss/remote-wake-sleep-on-lan-docker
My Repository: https://github.com/SmartPhoneLover/unraid-docker-templates

 

DESCRIPTION
The Remote Wake/Sleep-On-LAN Server (RWSOLS) is a simple webapp to remotely power up (wake) and power down (sleep) any supported device via WOL/SOL protocol.

 

NOTES
• If you want to use the 'SLEEP' function, additional software will be needed on the client: 'Sleep-On-LAN (SOL)'. A button to sleep the device will be shown, instead of wake device, when corresponding variables are set accordingly. Both 'wake' and 'sleep' options will be shown in the web interface according to the current state of the device.
• The values of Name, MAC and IP variables (RWSOLS_COMPUTER) must be intered in the following format: "xxx","xxx".
• There are other variables that you can use, if needed. Check the GitHub repo to know more.
• When changing the webserver's port, be sure to set the same port number in all corresponding fields on this template.
• The default password for the wake/sleep function (button) is: 'unRAID', but you can set your own. Leave it blank (do not delete the variable) if you don't want to enter any.

 

VERSION
1.1 (2022-05-26)


If you are going to report a bug or request something to be added/modified, please, take into consideration that I will only be able to apply changes for the work I own only. For example, if I create a docker template for an already existing docker image (not created by me), I won't be able to do more for that image than forward your report or request to the owner of the project.

Edited by SmartPhoneLover
Link to comment

Hey Hello there i have this error message, maybe i dont see the obvious solution for that

 

search_and_replace REPLACE_RWSOLS_COMPUTER_IP with 192.168.178.x
search_and_replace REPLACE_RWSOLS_COMPUTER_MAC with xx:xx:x:xx:x:xx
search_and_replace REPLACE_RWSOLS_COMPUTER_NAME with Tower
search_and_replace REPLACE_RWSOLS_MAX_PINGS with 15
search_and_replace REPLACE_RWSOLS_SLEEP_CMD with suspend
search_and_replace REPLACE_RWSOLS_SLEEP_PORT with 7760
search_and_replace REPLACE_RWSOLS_SLEEP_TIME with 5
search_and_replace port 8080 with 8099
Starting Apache2: /usr/sbin/apache2ctl -D FOREGROUND
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 192.168.178.2. Set the 'ServerName' directive globally to suppress this message

 

where can i set that "directive globally" :D 

 

i tryed reaasonable changes and even unreasonable

 

i tryed the MAC of my PC i want to wake and its Local IP

i tryed the MAC of my Unraidserver and its Local IP

 

both variants result in not finding its qualified domain name.. 

 

 

 

 

Link to comment

@domrockt

If the container works as expected after setting all the fields, the 'AH00558: Could not reliably determine the server's fully qualified domain name' error can be ignored safely. It does not prevent the Apache from running. Anyway, I will try to find a solution for the containers where the corresponding config files are not correctly configured by their devs.

 

I have created a little guide about how to disable this warning. You can check it here.

Edited by SmartPhoneLover
Link to comment

UPDATE

v1.1 (2022-05-26)

- New: Added 'PASSPHRASE' variable to allow using a password for the WebGUI.

- New: Added 'RWSOLS_MAX_PINGS' variable (declared only in the docker image) to configure the max number of ping calls to send to a device to detect its state.

- Fix: The configured webserver's port didn't match with the one set in 'WebUI' port field, my fault sorry. (It worked when I created the template, maybe because it was cached from previous testings)

- Other: Changed the webserver's port to 9999, to prevent posible conflicts with the default one (8080).

Link to comment
  • 1 month later...
  • 3 months later...

Hi there, just trying to get set up. I thought I'd gotten everything in correctly and the docker seems to be running but I can't access it. When I go to open the WebUI I just get an HTTP ERROR 500 with the message this page isn't working, "IP Address" currently unable to handle this request.

 

Editing to add: Got it figured out, must have made a mistake in my entries.

Edited by CS Ink
Link to comment
  • 2 weeks later...

I seem to be running into some sort of problem. Starting the container with the same variables set in the github yields a completely blank web page.

<html>
  <head></head>
  <body></body>
</html>

Logs just say:

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
search_and_replace REPLACE_RWSOLS_COMPUTER_IP with 192.168.1.5
search_and_replace REPLACE_RWSOLS_COMPUTER_MAC with 87:NC:R4:9N:W2:HV
search_and_replace REPLACE_RWSOLS_COMPUTER_NAME with HomePC
search_and_replace REPLACE_RWSOLS_MAX_PINGS with 15
search_and_replace REPLACE_RWSOLS_SLEEP_CMD with suspend
search_and_replace REPLACE_RWSOLS_SLEEP_PORT with 7760
search_and_replace REPLACE_RWSOLS_SLEEP_TIME with 5
search_and_replace port 8080 with 9999
Starting Apache2: /usr/sbin/apache2ctl -D FOREGROUND

Not sure what to do from here...

Link to comment
  • 2 months later...
On 10/23/2022 at 9:41 PM, CS Ink said:

Hi there, just trying to get set up. I thought I'd gotten everything in correctly and the docker seems to be running but I can't access it. When I go to open the WebUI I just get an HTTP ERROR 500 with the message this page isn't working, "IP Address" currently unable to handle this request.

 

Editing to add: Got it figured out, must have made a mistake in my entries.

Can you tell us what caused it? I'm running into the same issue and I can't seem to figure it out.

Link to comment
  • 3 weeks later...

I decided to mess with this app today because I have a desktop in my basement that I rarely use and thought it would be nice to remote in after waking it up. I too got the same errors as those above. Mainly, the HTTP ERROR 500. I went into the container and read the actual apache logs and PHP had trouble parsing the parameters from unRAID. 

 

The Fix:

I simply added quotes to my entries in unRAID template for Name/IP/MAC

 

After this, I could hit the simple apache GUI. Also note, I have this on a different network than my PC that I wanted to wake up. I had to go in and adjust the pre-defined windows firewall settings on the desktop and allow icmp ping from my docker vLAN. Though, the container did send the WOL message to my PC and wake it up, because this happens before the OS is online. But if you want it to stop sending the WOL messages, it will need to get echo request replies.

  • Thanks 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.