starred/ntfy

Fork 0

mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 08:26:00 +02:00

iphone) #941

New issue

Closed

opened 2026-05-07 00:28:58 +02:00 by BreizhHardware · 4 comments

BreizhHardware commented

2026-05-07 00:28:58 +02:00

Owner

Originally created by @vingerha on GitHub (May 10, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1332

🐞 Describe the bug

Hi, I may be asking for the expected response but still

I am using home-assistant to create notifications and I would like to use an action to trigger something back in HA.
After a bit of fumbling around I ended up with below message/object which actually works fine albeit only fromm my laptop or pc. The iPhone and iPad apps do not do anything, not even an error....and debugging is pretty tricky (for me)
Q1: is this a known issue for http?
Q2: any tips to get into more details of the issue?

Note: I can create this using either curl or home-assistant (via the hacs/ntfy integration)

{
    "id": "T5KRYBxD9k",
    "action": "http",
    "label": "Switch on",
    "clear": false,
    "url": "https://ip/api/services/switch/turn_on",
    "method": "POST",
    "headers": {
        "Authorization": "Bearer eyJhbG....",
        "Content-type": "application/json"
    },
    "body": "{\"entity_id\": \"switch.dockernuc_adsblol\"}"
}

💻 Components impacted
latest server running in docker on ubuntu 22.04
ios apps

💡 Screenshots and/or logs

Sadly no logs...ios (why oh why)

Originally created by @vingerha on GitHub (May 10, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1332 :lady_beetle: **Describe the bug**  Hi, I may be asking for the expected response but still I am using home-assistant to create notifications and I would like to use an action to trigger something back in HA. After a bit of fumbling around I ended up with below message/object which actually works fine albeit only fromm my laptop or pc. The iPhone and iPad apps do not do anything, not even an error....and debugging is pretty tricky (for me) Q1: is this a known issue for http? Q2: any tips to get into more details of the issue? Note: I can create this using either curl or home-assistant (via the hacs/ntfy integration) ``` { "id": "T5KRYBxD9k", "action": "http", "label": "Switch on", "clear": false, "url": "https://ip/api/services/switch/turn_on", "method": "POST", "headers": { "Authorization": "Bearer eyJhbG....", "Content-type": "application/json" }, "body": "{\"entity_id\": \"switch.dockernuc_adsblol\"}" } ``` :computer: **Components impacted** latest server running in docker on ubuntu 22.04 ios apps :bulb: **Screenshots and/or logs**  Sadly no logs...ios (why oh why)

BreizhHardware

2026-05-07 00:28:58 +02:00

closed this issue
added the
🪲 bug
label

BreizhHardware commented

2026-05-07 00:28:59 +02:00

Author

Owner

@wunter8 commented on GitHub (May 10, 2025):

I'm not sure why that would be. Maybe it's a certificate trust issue? iOS doesn't trust your Home Assistant cert but your other devices do??

As an initial debug, try sending an http request to another website, such as one at https://webhook.site.

I just tested it with the following request, and things worked fine: curl -d 'test' -H "Action: http, test, https://webhook.site/7dece5c9-c5ae-47c6-98e9-23487063a492, method=POST, headers.Authorization=Bearer here, headers.Content-Type=application/json, body={\"action\": \"turn on\"}" https://ntfy.domain.com/test

@wunter8 commented on GitHub (May 10, 2025): I'm not sure why that would be. Maybe it's a certificate trust issue? iOS doesn't trust your Home Assistant cert but your other devices do?? As an initial debug, try sending an http request to another website, such as one at https://webhook.site. I just tested it with the following request, and things worked fine: `curl -d 'test' -H "Action: http, test, https://webhook.site/7dece5c9-c5ae-47c6-98e9-23487063a492, method=POST, headers.Authorization=Bearer here, headers.Content-Type=application/json, body={\"action\": \"turn on\"}" https://ntfy.domain.com/test`

BreizhHardware commented

2026-05-07 00:28:59 +02:00

Author

Owner

@vingerha commented on GitHub (May 11, 2025):

Appreciate the return, thanks and this goes a bit beyond my level of exp.

This is what I used

curl -d 'test' -H "Actions: http, test, https://webhook.site/b5243d18-blablabla, method=POST, headers.Authorization=Bearer here, headers.Content-Type=application/json, body={\"action\": \"turn on\"}" ntfy.vingerhoeds.synology.me/test

The same notification, from 3 devices on the same network (same wifi AP) and 3 diff. results

via the laptop, this looks resolvable to me, it shows my isp address and the https of my ntfy. Compared to the other two, I cannot see the body represented in the 'Request content' section...odd. It also shows a REST 'OPTIONS' instead of a'POST' for the ones below
It does throw a cors error, this I had before on the home assistant server too but that I got resolved on HA itself.

via the iphone, here the host is converted, the referer/origin disappear. What might be the case is that my company, who provides and administres the phone, may have added some blockers to reduce security risks. ... I suggest we skip this for now as I have no control over its settings. This 'host' is however different from the ipad host.

via the iPad using Chrome, here the host is converted as well, different from ht eiphone, here referrer /origin are visible

via the iPad using the app, host the same as for the Chrome, but no referrer or origin

@vingerha commented on GitHub (May 11, 2025): Appreciate the return, thanks and this goes a bit beyond my level of exp. This is what I used ``` curl -d 'test' -H "Actions: http, test, https://webhook.site/b5243d18-blablabla, method=POST, headers.Authorization=Bearer here, headers.Content-Type=application/json, body={\"action\": \"turn on\"}" ntfy.vingerhoeds.synology.me/test ``` The same notification, from 3 devices on the same network (same wifi AP) and 3 diff. results 1. via the laptop, this looks resolvable to me, it shows my isp address and the https of my ntfy. Compared to the other two, I cannot see the body represented in the 'Request content' section...odd. It also shows a REST 'OPTIONS' instead of a'POST' for the ones below It does throw a cors error, this I had before on the home assistant server too but that I got resolved on HA itself. ![Image](https://github.com/user-attachments/assets/9efcf585-6ea9-4a19-bb71-2062c7d00106) 2. via the iphone, here the host is converted, the referer/origin disappear. What might be the case is that my company, who provides and administres the phone, may have added some blockers to reduce security risks. ... I suggest we skip this for now as I have no control over its settings. This 'host' is however different from the ipad host. ![Image](https://github.com/user-attachments/assets/b73b2f7e-6cb4-4c07-ba52-e6ba8596168c) 3. via the iPad using Chrome, here the host is converted as well, different from ht eiphone, here referrer /origin are visible ![Image](https://github.com/user-attachments/assets/b8f12293-319d-4390-9088-05c2f4d32df1) 4. via the iPad using the app, host the same as for the Chrome, but no referrer or origin ![Image](https://github.com/user-attachments/assets/a7d08c79-7e70-429f-b0c2-8de760b031b2)

BreizhHardware commented

2026-05-07 00:28:59 +02:00

Author

Owner

@vingerha commented on GitHub (May 11, 2025):

Update... I got someone elses android tablet to test too and that one kicked back a 'hostname [servername] not verified] and with some digging I added a certificate to the sub(!)-domain on which my HA is installed and lo-and-behold.... it works now also on iPhone and iPad.
Closing this ticket and thanks for the feedback

@vingerha commented on GitHub (May 11, 2025): Update... I got someone elses android tablet to test too and that one kicked back a 'hostname [servername] not verified] and with some digging I added a certificate to the sub(!)-domain on which my HA is installed and lo-and-behold.... it works now also on iPhone and iPad. Closing this ticket and thanks for the feedback

BreizhHardware commented

2026-05-07 00:28:59 +02:00

Author

Owner

@vingerha commented on GitHub (May 11, 2025):

Another update. I found out the issue. My server is on a subdomain via revproxy. My ha is on name.synology.me, the devserver that I am testing is on hadev.name.synology.me. For the latter there was a sercurity warning as the certificate for the main doman was not working on the subdomain (my lack of knowledge). This I could only find via someone elses android tablet that finally threw a logicla error. After adding a cert. for the subdomain all is working..laptop/pc, tablet, phone on ios and android

@vingerha commented on GitHub (May 11, 2025): Another update. I found out the issue. My server is on a subdomain via revproxy. My ha is on name.synology.me, the devserver that I am testing is on hadev.name.synology.me. For the latter there was a sercurity warning as the certificate for the main doman was not working on the subdomain (my lack of knowledge). This I could only find via someone elses android tablet that finally threw a logicla error. After adding a cert. for the subdomain all is working..laptop/pc, tablet, phone on ios and android

BreizhHardware referenced this issue

2026-05-07 01:02:15 +02:00

[PR #941] [MERGED] Append /v2 to module so version 2 can be used as a go package #1470