then I copied the public and private key (VAPID) I had from my Windows deploy and put it in the properties of the pushserver component.
Current status: when a message is to be pushed: I get a 403 :-(
So I guess it is back to the VAPID keys: the page mentionned above says I need libWebPush.so, but I can't find it anywhere on my PC (WebPush.dll for Windows uis there in the demo folder)
There seems to be a bug in TTMSFNCCustomWebPushSender.InternalSendNotification:
the local variable ssl is not being initialized: it causes an access violation as it will point to a random address (for some reason in Windows it does not seem to matter). So I fixed it by ssl := nil at the beginning of the method
Also: the call to /vapidPublicKey for the first time will generate a push.ini file with the keys now (as well as returning it the public key in JSON to the client), however in Linux the call then will cause the application to close unexpectedly. When the key can be read from the file afterwards all is ok: I could not fully pinpoint it (it seems somethin i the IndyHTTPServer). I meanwhile fixed it by calling FVapidSettings.InitializeKeys in TTMSFNCCustomWebPushServer.Create
The ssl variable not being initialized was meanwhile solved in the latest version (there was also a ticket on this in this forum), but as I needed to revert to the version before (because of the missing libWebPush.so), ... I cam across this bug again.