API commands via Apple Shortcuts app (request time out)

[powernapper]

Hello!

First off, this project is great. I really appreciate the functionality and ease of use.

I am in the process of making an iOS shortcut to wake one of my devices using the API. I am running into an issue where the endpoint for the [GET] /api/upsnap/wake/:id times out. It seems to wake the device correctly, but I am not sure the API is responding to the request appropriately and there are no logs relating to the wake request even though the auth request are logged.

More info below:

iOS shortcut so far:

1. Dictionary

• UpSnap URL : [url of my upsnap instance - using nginx proxy manager to use a subdomain]
• identity : [my upsnap login email]
• password : [my upsnap login password]
• ID-DesktopPC : [the upsnap id for my desktop pc]

2. URL
   (UpSnap URL)/api/collections/_superuser/auth-with-password

3. Get Contents of (URL)
   method: POST
   Headers: Content-Type : application/json
   Request Body: JSON

• identity : (identity)
• password : (password)

4. Get (Value) for (token) in (Contents of URL)

5. URL
   (UpSnap URL)/api/upsnap/wake/(ID-DesktopPC)

6. Get Contents of (URL)
   Method: GET
   Headers

• Authorization : (token)

The issue I'm running into is that the step 6 request times out. Checking the logs at [my upsnap URL]/_/#/logs confirms that the [POST] auth request is being received, but there is no log showing the [GET] wake request.

The PC I am waking with the [GET] wake request appears to be waking, but when there is no response from UpSnap, the request times out, which prevents the Shortcut from moving on. Is is normal to not receive a 200 OK response for this kind of API request? How should I go about fixing this?

Edit:

In doing some more digging, the docker logs DO show the wake request, but not the API logs. However, the docker logs show that the PC is not online after 120 seconds, so there may be an issue with the PC responding to pings from the docker container. I added the UpSnap via docker compose with "network_mode: host" and also with "cap_add: -NET_RAW" but am still getting the issue with UpSnap being unable to determine that the PC is online, and also that my API request for the wake is timing out (even though it is going through).

[powernapper]

Okay, so afterall, it was related to the firewall settings on my PC. For anyone who stumbles across this in the future, I followed the steps for Windows Firewall found here https://servicenow.iu.edu/kb?id=kb_article_view&sysparm_article=KB0025160

[seriousm4x]

Version 5.1.0 (released today) features a new async parameter to the wake request. /api/upsnap/wake/[id]?async=true which will directly return the api response and not wait for the pc to wake up. The shortcut will finish immediately.

[powernapper]

I think this is a good overall change, but I am glad I was able to resolve the issue by configuring my PC's windows firewall. Thanks for the quick response.