What could have caused Mattermost mobile alerts from happening after updates?

Troubleshooting Mobile Apps
1

Our community / Team version of Mattermost was delivering messages to mobile devices without a problem until a few updates ago. Is there anything that would have stopped this from occurring?

2

We recently migrated the TPNS, and HPNS servers, which would have resulted in a change of IP addresses. I would suggest to restart the Mattermost servers and also flush the DNS cache for good measure.

3

Thank you. I thought I would try to see if this issue would occur on a fresh setup since I have yet to be able to resolve this and folks have been complaining a lot about still not getting alerts on their devices as they used to, but even a new Teams setup does not work. Neither of these installations are commercial / paid for installations, but alerts were fine up until some certain update.

4

Something I was not aware of before for lack of looking, the following are appearing in the /opt/mattermost/logs/notifications.log:

{"timestamp":"2024-05-15 06:16:04.188 Z","level":"error","msg":"Failed to send to push proxy","caller":"app/notification_push.go:192","logSource":"notifications","type":"push","status":"not_sent","reason":"push_proxy_error","ack_id":"XXXX","push_type":"clear","user_id":"XXXX","device_id":"XXXX","error":"failed to decode from JSON: EOF"}
{"timestamp":"2024-05-15 06:16:04.270 Z","level":"error","msg":"Failed to send to push proxy","caller":"app/notification_push.go:192","logSource":"notifications","type":"push","status":"not_sent","reason":"push_proxy_error","ack_id":"XXXX","push_type":"clear","user_id":"XXXX","device_id":"XXXX","error":"failed to decode from JSON: EOF"}
{"timestamp":"2024-05-15 06:16:04.346 Z","level":"error","msg":"Failed to send to push proxy","caller":"app/notification_push.go:192","logSource":"notifications","type":"push","status":"not_sent","reason":"push_proxy_error","ack_id":"XXXX","push_type":"clear","user_id":"XXXX","device_id":"XXXX","error":"failed to decode from JSON: EOF"}
{"timestamp":"2024-05-15 06:16:04.424 Z","level":"error","msg":"Failed to send to push proxy","caller":"app/notification_push.go:192","logSource":"notifications","type":"push","status":"not_sent","reason":"push_proxy_error","ack_id":"XXXX","push_type":"clear","user_id":"XXXX","device_id":"XXXX","error":"failed to decode from JSON: EOF"}
{"timestamp":"2024-05-15 06:17:15.854 Z","level":"error","msg":"Failed to send to push proxy","caller":"app/notification_push.go:192","logSource":"notifications","type":"push","status":"not_sent","reason":"push_proxy_error","ack_id":"XXXX","push_type":"message","user_id":"XXXX","device_id":"XXXX","error":"failed to decode from JSON: EOF"}
{"timestamp":"2024-05-15 06:17:15.931 Z","level":"error","msg":"Failed to send to push proxy","caller":"app/notification_push.go:192","logSource":"notifications","type":"push","status":"not_sent","reason":"push_proxy_error","ack_id":"XXXX","push_type":"message","user_id":"XXXX","device_id":"XXXX","error":"failed to decode from JSON: EOF"}
{"timestamp":"2024-05-15 06:17:16.010 Z","level":"error","msg":"Failed to send to push proxy","caller":"app/notification_push.go:192","logSource":"notifications","type":"push","status":"not_sent","reason":"push_proxy_error","ack_id":"XXXX","push_type":"message","user_id":"XXXX","device_id":"XXXX","error":"failed to decode from JSON: EOF"}
{"timestamp":"2024-05-15 06:17:16.087 Z","level":"error","msg":"Failed to send to push proxy","caller":"app/notification_push.go:192","logSource":"notifications","type":"push","status":"not_sent","reason":"push_proxy_error","ack_id":"XXXX","push_type":"message","user_id":"XXXX","device_id":"XXXX","error":"failed to decode from JSON: EOF"}
5

Wow - just found the issue it appears config.json must have PushNotificationServer set to use https instead of http, which had been a default from several years of use.