Add matrix.org pushers IP adresses to the allow list, to avoid rate limiting.

[bmarty]

Hello,

Following discussion which occurred here, here is the list of IP addresses that should not be rate limited (or maybe with a higher limit?) for matrix.org users:

• 176.126.240.157
• 176.126.240.158
• 176.126.240.212
• 176.126.240.216

And their IPv6 equivalent:

• 2a00:1098:84:1c8::157
• 2a00:1098:84:1c8::158
• 2a00:1098:84:1c8::1:1
• 2a00:1098:84:1c8::2:1

There is no hostname associated with those addresses, but they have been stable since more than 4 years now.

Thanks!

[binwiederhier]

These have been whitelisted for years: https://github.com/binwiederhier/ntfy-ansible/blob/main/roles/ntfy/templates/server.yml.j2#L282

[DocSniper]

Did I miss something, or are the IPv6 addresses missing in this file ?

[bmarty]

Thanks @binwiederhier . What could explain that ntfy.sh does not send Push when it's requested by the matrix.org homeserver then?

[Saturn745]

Is there any update on this? I have an account on matrix.org, and I am using ntfy.sh for notifications, but they don't go through at all.

[DocSniper]

I tested the instance of adminForge, here the notification works for Element and Element X as expected.
This may be a problem of the ntfy.sh instance.

[dav23r]

My account on matrix.org doesn't publish notifications to ntfy.sh for some weeks already. (I used FluffyChat and Element as android clients). - there are no messages on the web page under the topic feed.