
Rogers Fixes MMS Not Working: ‘Proxy Authentication Required’ [Update]
Image via @deanaruston
Some Rogers customers are dealing with an MMS error this morning, with a pop-up mentioning ‘Proxy Authentication Required’. Update: this issue has now been fixed according to Rogers.
The issue seems to affect regular MMS messages including group MMS chats, but does not affect iPhone users and iMessage. The ‘Proxy Authentication Required’ message says, “enter the password for the HTTP proxy mmsproxy.rogers.com:80”.
.@RogersHelps, Group MMS messages are not sending. iMessages are sending without issue and no problems. I am a @Rogers Corporate account. I have restarted my phone several times but still no success. Please help. I am also receiving the below error, please see photo attached.… pic.twitter.com/mZiESKlp5B
— Deana Ruston 🇨🇦 ♿️ (@deanaruston) May 18, 2023
@RogersHelps I keep getting a message about proxy authentication… how do I fix it?
— María Piña (@mcamiller) May 18, 2023
@Rogers why is my MMS not working? I keep getting a "network error" when trying to receive multimedia messages.
— Christina Mac (@btchristinamac) May 18, 2023
Rogers responded to numerous customers on the MMS issue to say, “We’ve received reports of some customers experiencing an issue sending MMS messages and our network team is working to resolve as quickly as possible. Thank you for your understanding and patience.”
Any Rogers wireless outages nowadays can bring back some nightmares related to last year’s nationwide shutdown.
Are group MMS chats working for you on Rogers right now? Rogers has yet to mention if the issue is fixed or not. Stay tuned as we’ll provide updates when available.
Some iPhone in Canada readers noted this error is still happening and has been four hours and counting now.
Good morning west coast bloggers! It's been 4 hours for me.
— Chris Clarke (@clarkey) May 18, 2023
Update May 18, 2023, 9:14am PDT: A Rogers spokesperson confirmed with iPhone in Canada there was a “brief intermittent MMS interruption” this morning for some customers, and has since been fixed.
Thanks James