element-android icon indicating copy to clipboard operation
element-android copied to clipboard

local ntfy server not handled properly

Open ne20002 opened this issue 2 years ago • 2 comments

Steps to reproduce

I wanted to set up a local ntfy server to use with my Synapse and Element. It is working well except for Element. The problem seems to be the http and port of the server.

When I enter ntfy.sh as default server in the Android ntfy app, Element subscribes to a topic on ntfy.sh and the config looks like this: grafik All working properly.

If I enter my own local homeserver in the ntfy app with the address http://192.168.40.2:8080 it is not working. In this case, Element subsribes (as seen in the ntfy app) but the configuration in Synapse looks like: grafik

Outcome

What did you expect?

I expect the local address o fmy ntfy server handled properly. I don't know if it is a probem within Element or Synape.

What happened instead?

Notifications not working

Your phone model

Samsung S10e

Operating system version

/e/OS 1.18 (Android S)

Application version and app store

Element 1.6.6 from F-Droid

Homeserver

Synapse 1.98 docker image

Will you send logs?

No

Are you willing to provide a PR?

No

ne20002 avatar Dec 15 '23 12:12 ne20002

I took a deeper look and it seems that

  • the problem is caused due to the http, thus not using https
  • the next version 1.6.8 might fix this for the app (1.6.8 is not on F-Droid until now)

But the comment in the commit fixing the check on ssl (why is this done if protocol is http?) ignoring a failure of ssl probing states that the ssl check is also done by the server. So I keep this open until I can recheck with 1.6.8 if the problem is fixed.

ne20002 avatar Dec 15 '23 19:12 ne20002

This is still a problem with Element Android 1.6.10 and Synapse 1.99.0 (docker image).

ne20002 avatar Jan 20 '24 11:01 ne20002

I fixed this by adding TLS to my internal Ntfy-Server. I now have another problem.

ne20002 avatar Mar 16 '24 11:03 ne20002