Hello, Thanks for the Nodered node works 
. My problem is that the URL is not called correctly after clicking on the received message. I have the dashboard via a reserve proxy with ssl. The URL is https://domain, but it calls http://domain/ui can I change the setting?
thank you mfg
Hi @EIKSEU,
I am going to share the link to your Github issue here also. Posting the same question simultaneously on two locations won't speed up the process of getting feedback...
I assume then that there is a bug then in my code that determines the dashboard path (see here). You can search that web_push_client.js file on your filesystem, and set the dashboardPath for example by a hardcode path of your choice until it works. If I know what is wrong in that code snippet (to determine the dashboard path) for your use case, I can try to fix it afterwards.
Bart
Hello, thanks for the quick response, will continue to write here, ok?
I've now entered the correct path at that point but it still appends /ui... and thus opened incorrectly the rest of the path is correct.
Kind regards
Hmm, that is not what I had expected. Although it is quite a long time ago that I worked on that node, and I might be mistaken...
- Can you share a screenshot of the code snippet with your change. Just to make sure you have manipulated the code correctly.
- That code is inside an endpoint that is called by your browser to load the nodered_push_service.js file, which will contain your manipulated path. But your browser has cachec that file, so it might be that he keeps using the old cached file (containing the old path). Can you try the flow here on my readme page. When you inject the message, the browser should reload that file.
- If that doesn't work, can you try by clearing your browser cache?
- And if that doesn't work, can you try to find that file somewhere in your browser developer tools? I don't know by head, but I can have a look tonight after work
Ok suddenly it works ... was probably still in the cache. Should that meanwhile also work with an I-Phone?
Ah ok, that is good news.
Am I correct that there is no way for my node to calculate your path, since your reverse proxy determines it outside of Node-RED? If that would be the case, my node should offer a way to enter the path manually via the node's config screen?
Don't know, I'm not welthy enough to buy Apple stuff 
LMGTFY:
In Safari 16 in macOS 13 or later, Safari supports web push — push notifications that use the cross-browser Push API, Notifications API, and Service Worker standards.
But I have no clue whether my node will work. If you are lucky then somebody will test it, fix it and do a pull request to make sure my node can support Apple devices. But I would not count to much on that ...
Actually, the url domain is recognized, only "/ui" was always appended at the end,
...yes, that would also be a possibility if you can simply specify the url yourself.
I also tried the node on an iPhone because Apple now offers web push, but this brings an error "Cannot get subscription from serviceworker: AbortError: No connection to push daemon" This error comes immediately when the website opens without pressing the button. ..and the button is no longer clickable.
can you tell me something about "https://discourse.nodered.org/t/apache2-reserve-proxy-mp4"?
Thank you Mfg
As mentioned above, if somebody will do a pull request for iPhone I will be happy to merge it.
But I don't have free time enough to digg into this at the moment. Moreover I prefer to migrate my stuff to the Flexdash from @tve, instead of keep spending my time developing stuff in my old ui nodes for the old dashboard.
Otherwise my stuff will never end up in Flexdash...
Ok thanks for the knot and your help.
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
