# What could have caused Mattermost mobile alerts from happening after updates? **URL:** \ **Category:** Mobile Apps\ **Created:** [March 24, 2024, 11:07pm UTC](https://forum.mattermost.com/t/what-could-have-caused-mattermost-mobile-alerts-from-happening-after-updates/18256 "2024-03-24T23:07:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ylluminate](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/ylluminate/32/2253_2.png) [@ylluminate](https://forum.mattermost.com/u/ylluminate)\ **Post date:** [March 24, 2024, 11:07pm UTC](https://forum.mattermost.com/t/what-could-have-caused-mattermost-mobile-alerts-from-happening-after-updates/18256/1 "2024-03-24T23:07:22Z")
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? ---
**Author:** ![agnivade](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/agnivade/32/3846_2.png) [@agnivade](https://forum.mattermost.com/u/agnivade)\ **Post date:** [March 27, 2024, 5:39am UTC](https://forum.mattermost.com/t/what-could-have-caused-mattermost-mobile-alerts-from-happening-after-updates/18256/2 "2024-03-27T05:39:43Z")
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. ---
**Author:** ![ylluminate](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/ylluminate/32/2253_2.png) [@ylluminate](https://forum.mattermost.com/u/ylluminate)\ **Post date:** [April 28, 2024, 8:59pm UTC](https://forum.mattermost.com/t/what-could-have-caused-mattermost-mobile-alerts-from-happening-after-updates/18256/3 "2024-04-28T20:59:39Z")
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. ---
**Author:** ![ylluminate](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/ylluminate/32/2253_2.png) [@ylluminate](https://forum.mattermost.com/u/ylluminate)\ **Post date:** [May 15, 2024, 6:26am UTC](https://forum.mattermost.com/t/what-could-have-caused-mattermost-mobile-alerts-from-happening-after-updates/18256/4 "2024-05-15T06:26:33Z")
Something I was not aware of before for lack of looking, the following are appearing in the `/opt/mattermost/logs/notifications.log`: ```auto {"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"} ``` ---
**Author:** ![ylluminate](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/ylluminate/32/2253_2.png) [@ylluminate](https://forum.mattermost.com/u/ylluminate)\ **Post date:** [May 15, 2024, 7:08am UTC](https://forum.mattermost.com/t/what-could-have-caused-mattermost-mobile-alerts-from-happening-after-updates/18256/5 "2024-05-15T07:08:53Z")
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.