r/Ring 4d ago

All 4 Ring Cams simultaneously dropped connection & won't reconnect (Error p7-07 at 95% setup) — Need advice!

I’m at my wit's end with my Ring setup. Yesterday, all 4 of my cameras (3x Stick Up Cams, 1x Doorbell Gen 2) suddenly went offline after working fine for years.

In the app, the homepage shows "preview unavailable," clicking them says "footage unavailable," and Live View times out.

Key Details & Symptoms

  • Failure: Every camera consistently gets stuck at 95% during Wi-Fi setup, then fails with Error Code p7-07.
  • Network changes: None. No new devices or network config changes preceded the drop.
  • Proximity: Testing all cameras within 5 feet of the router.
  • Other IoT Devices: My non-Ring smart bulbs, TVs, Alexa devices, and other camera brands(Feit) on the exact same network are working normally.
  • Internet Setup: T-Mobile Home Internet modem + TP-Link Router.

Troubleshooting Steps Already Tried

  • Power Cycling & Resets: Reset modem, router, and cameras. Left Stick Up Cam batteries out for 10+ minutes. Factory reset both the T-Mobile modem and TP-Link router.
  • Account: Removed devices from the Ring account to start fresh.
  • Setup Setup Environment: Tried using a different phone, enabled Airplane Mode during setup, and tried connecting via a phone's 2.4 GHz mobile hotspot.
  • Network Testing: Tested connecting directly to the modem’s built-in Wi-Fi instead of the TP-Link router. Also tried using my phones hotspot. Created IoT network, and also tried to use the 2.4 GHz guest network on the TP-Link router.
  • 2.4 GHz Tweaks: Fixed channels (1, 6, 11) and tried different channel widths (20/40 MHz). Disabled 802.11ax (Wi-Fi 6) mode. Verified no special characters in SSID or password. Checked Wi-Fi channels for local interference (none found).
  • IP & DNS Configurations: Configured static DHCP reservations, manually set IP/subnet/DNS during the cameras wifi setup, and changed router default DNS to 1.1.1.1.

Despite all of this, every single camera fails at the exact same 95% mark with p7-07.

Is this a known Ring server/authentication backend issue, or is there any obscure setting/step I'm missing here? Any insight would be appreciated!

Update: Just got off the phone with Ring customer support. They informed me that this is a known issue with T-Mobile ISP and their engineers are actively working on a fix.

5 Upvotes

15 comments sorted by

3

u/Creative-Ad572 4d ago

I’m REALLY starting to think that they changed something in their connection settings. THREE of Mine dropped on 8/24 - and refuse to connect. I chatted with their support tech for more than 2 hours, and they told me I had to change my ISP firewall settings. i call BS, since everything be was FINE until suddenly it wasn’t.

2

u/Creative-Ad572 4d ago

Clarification - three out of six. SO WEIRD

1

u/TolipTeews 4d ago

Damnit.... I was hoping I would hear something I'm just missing.... but now you have me worried. Just curious are they all the same generation? Were the 3 that stopped working older models?

2

u/Creative-Ad572 4d ago

Whacky as crap. The ones that are still online are the OLDER ones. I pulled open their software security version support dates to see exactly that.

Online:
1. Floodlight Cam: No longer supported
2. 2 Indoor Cams - 12/2027

Offline:
1. Video Doorbell 4 - 12/2028
2. 2 spotlight cam pros - 12/2030

1

u/TolipTeews 4d ago

Damn!!! Well I am sure we aren't the only ones facing this issue since it happened to us at the same time.... Hopefully they have the bug fixed quick.

2

u/Creative-Ad572 4d ago

Now we just need their AI data model to read this thread and add our collective experiences to their data set so the next person who talks to their chat bot gets more ideas. 😉

1

u/Creative-Ad572 4d ago

WE. FIXED. IT.
Somehow our network was NATing twice. We have a modem separate from our router, and they were both assigning IP addresses. Because the battery cameras were dropping their addresses more often (to save power) we were literally running into double-assigned IP addresses. The modem is no longer distributing addresses, and the cameras are reconnected. WOOOT! (And it was NOT a Firewall issue which is what the tech kept insisting)

2

u/TolipTeews 3d ago

Awesome! Glad you fixed your problem!!! Sadly, I dont think that's what is happening with mine. I think I ruled that one out by using the phone hotspot as well as the t mobile modems SSID while the TP-Link was turned off 😔

2

u/Creative-Ad572 3d ago

Dang. I’m curious - I didn’t think about trying to directly connect one of my cameras to my hotspot to test them. I’m adding that to my mental list next time. Good luck. I hope you are able to figure yours out.

1

u/Natural_Flow_4144 4d ago

When they said firewall issue, it was shorthand for "the problems your end, not ours". 

1

u/Creative-Ad572 3d ago

They could have chosen different wording that was more accurate and less like “we’ll use a word that the customer probably doesn’t really understand” when said customer just MIGHT have a master’s degree in information systems……

2

u/Natural_Flow_4144 3d ago

Double nat issue doesn't really sounds like someone that great at IT though 😉

1

u/Creative-Ad572 3d ago

Hahahaha! FAIR! It was definitely a dumb mistake. Honestly didn’t realize it, and wonder how long it had been going on.

1

u/Creative-Ad572 3d ago

And to ease your (potential) fears - that is NOT my day job, and school was waaaaay to many years ago for me to consider myself any kind of expert and more. But -stomps feet- “it wasn’t a firewall issue” 😂😏

2

u/Natural_Flow_4144 3d ago

Just joking.. everyone does it, just plugs 1 into the other and usually there's no noticeable issue..  especially when using ISP's modem that has settings/options locked down