Hello @Manoj,
I am looking forward to release 4.1.
I have made an observation regarding push.murena.com: I sometimes get a 502 error when accessing the URL of a topic channel. This may be the reason that e.g. my Molly messages sometimes arrive only if I open the app. [1] I also sometimes get an error with UP-Example for the same reason. [2]
These 502 errors have appeared several times during the last week.
Could you ask the infrastructure team whether there are currently some problems with push.murena.com, e.g. during the evening, when there may be a larger workload?
If possible, I would also suggest to update the nginx installation that is used as a reverse proxy because it is a legacy version. [3]
[1] I am using mollysocket.yourdevice.ch as Molly Socket server, which reliably works.
[2] I use version 2.2.0 because newer versions do not recognize foundation.e.ntfy, as noted in the backlog.
[3] The 502 error page is a default error page from the nginx installation and includes the server version. While “security by obscurity” is not generally a good idea, I have also read that web servers should not expose their respective version, which includes the server header in the response. On the other hand, I could not write this if the version were not shown. 