Scheduled Wake On Lan

[Sebastian Roth]

@Petěrko I have not found the time to dive into this yet.

I am wondering if it’s along the lines of what @altitudehack posted in the other topic. @Tom-Elliott has worked on the code and maybe knows more about it already?!

[Petěrko]

@sebastian-roth Hi, today I found time to install Ubuntu Server 20.04.2 on Bare Metal and KVM (Proxmox). With HTTPS enabled and disabled. Master and DEV-branch. It looks like https problem but I will test it once more to be sure.

Scheduled WOL is working on:
1.5.9 on Ubuntu (KVM/Baremetal) with https DISABLED

Scheduled WOL is not working on:
1.5.9 on Ubuntu with https ENABLED
19.5.75 on Ubuntu with https ENABLED

I will continue on that in @altitudehack 's topic.

Peter

[Petěrko]

@sebastian-roth
I can confirm now. Https setting during install is the culprit.

Debian10 VM 1.5.9
http - instant WOL OK, scheduled WOL - working
https - instant WOL OK, scheduled WOL - not working

Peter

[Petěrko]

What about this (from other_vhosts_access.log)?

x.x.x.x:443 x.x.x.x - - [27/Apr/2021:10:30:11 -0400] "GET //fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"

Double leading forward slashes (//fog/…).
A typo? Or is it correct? Just a guess

Source: web/lib/fog/fogbase.class.php

$url = '%s://%s/fog/management/index.php?';
$url .= 'node=client&sub=wakeEmUp';

Peter

[Tom Elliott]

@petěrko The 200 code tells us that the response was successful.

The sprintf call defines httpproto. So while there may be a typo, this is unlikely the thing causing the issue you’re seeing.

[Petěrko]

@tom-elliott Thanks for reply and your great work, Tom.
I am looking into it again with more detail.

HTTP Cron WOL
port 80, POST, status 200
HTTP Cron WOL working

x.x.x.x:80 x.x.x.x - - [28/Apr/2021:02:51:07 -0400] "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 5068 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"

HTTPS instant WOL
port 443, POST, status 200
HTTPS Instant WOL working

x.x.x.x:443 x.x.x.x - - [28/Apr/2021:03:17:13 -0400] "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"

HTTPS Cron WOL
port 80, POST, status 302
and
port 443 GET,status 200
HTTPS Cron WOL not working

x.x.x.x:80 x.x.x.x - - [28/Apr/2021:03:23:20 -0400] "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 302 580 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"
x.x.x.x:443 x.x.x.x - - [28/Apr/2021:03:23:20 -0400] "GET //fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"

Is POST with status 302 on port 80 ok? It may be redirection to https, I guess.

I think GET for HTTPS is wrong. It gives 200 but I think server doesnt have enough info what to wake up.

Or am I wrong?
Peter

[Petěrko]

Update: Same on 1.5.9.77
Peter

[Tom Elliott]

@petěrko Well a redirect from 80 to 443 via 302 will take the post request and send it as get (meaning the mac address it’s intending to receive is missing)

I can attempt to iterate through beginning with https

[Tom Elliott]

@petěrko I altered the code to run through:

https:// AND http:// (in order)
so that wakeOnLAN should run regardless of which protocol you send (and more directly in the case you have a 302 redirect from http to https.

Please give it a try and let me know if it works.

Thank you,

[Sebastian Roth]

@petěrko said in Scheduled Wake On Lan:

Is POST with status 302 on port 80 ok? It may be redirection to https, I guess.
I think GET for HTTPS is wrong. It gives 200 but I think server doesnt have enough info what to wake up.

Great work! Thanks heaps for testing in detail and posting here.

As Tom said, it happens to be redirected to HTTPS (443) when sending a POST to HTTP (80). There is a good explanation on why this happens on stack exchange: https://softwareengineering.stackexchange.com/questions/99894/why-doesnt-http-have-post-redirect

[Petěrko]

@tom-elliott
@Sebastian-Roth

Thank you all. It is solved now in 1.5.9.78 with HTTPS on.

/var/log/apache2/other_vhosts_access.log

80 "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 302 599 
443 "GET //fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111 
443 "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111 

/opt/fog/log/fogscheduler.log for Power Management Task

[04-29-21 6:16:25 am]  * 1 task found.
[04-29-21 6:16:25 am]  * 0 scheduled task(s) to run.
[04-29-21 6:16:25 am]  * 1 power management task(s) to run.
[04-29-21 6:16:25 am]  * Power Management Task run time: Thu, 29 Apr 2021 06:16:00 +0000
[04-29-21 6:16:25 am]  * This is a cron style task that should run at: 1619676960.
[04-29-21 6:16:25 am]  * Found a wake on lan task that should run.
[04-29-21 6:16:25 am]  | Task sent to fcaa-https

/opt/fog/log/fogscheduler.log for Scheduled Task:

[04-29-21 6:22:26 am]  * 1 task found.
[04-29-21 6:22:26 am]  * 1 scheduled task(s) to run.
[04-29-21 6:22:26 am]  * 0 power management task(s) to run.
[04-29-21 6:22:26 am]  * Scheduled Task run time: Thu, 29 Apr 2021 06:22:00 +0000
[04-29-21 6:22:26 am]  * This is a cron style task that should run at: 1619677320
[04-29-21 6:22:26 am]  * Found a scheduled task that should run.
[04-29-21 6:22:26 am]            - Is a host based task.
[04-29-21 6:22:26 am]            - Unicaset task found!
[04-29-21 6:22:26 am]            - Host fcaa-https
[04-29-21 6:22:26 am]            - Task started for host fcaa-https!

Thank you again! Now our school can wake-up on Schedule

Peter