Your Base Station could not be discovered.

[mcho]

I stopped using Arlo cameras for about 18 months and unplugged everything.  When I reinstalled every thing I could not get the base unit discovered by my account with no hint from Arlo what the problem might be.   I read all the other similar posts  but all of them had different circumstances.

I did a factory reset several times to no avail. I turned the firewall on my router off.  I got out my original VMB3000 and old camera. Same issues.   I use Linux and Firefox with heavy security so I installed a vanilla version of Firefox. That didn't work. Switched to a Windows 10 machine with zero security and used  a fresh intall of Firefox and no luck.

My router can see both base units, VMB 3000 and VMB 4000 and according to the logs is communicating with Arlo servers.  MY guess is that the problem is with Arlo. 

The internet light is constantly blinking in a random pattern that suggests that two way communication is occurring with someone.

Here is a partial list of the servers contacted during the attempted handshake:

5/21/2022 11:59:00 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:59:00 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:57:56 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:57:56 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:56:53 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:56:53 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:55:50 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:55:50 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:55:40 AM 192.168.0.64 time-c.netgear.com
5/21/2022 11:55:40 AM 192.168.0.64 time-c.netgear.com
5/21/2022 11:54:48 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:54:48 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:53:46 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:53:45 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:52:42 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:52:42 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:52:39 AM 192.168.0.64 time-b.netgear.com
5/21/2022 11:51:39 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:51:39 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:51:06 AM 192.168.0.64 time-c.netgear.com
5/21/2022 11:51:06 AM 192.168.0.64 time-c.netgear.com
5/21/2022 11:50:40 AM 192.168.0.64 arlostatic-z2.arlo.com
5/21/2022 11:50:40 AM 192.168.0.64 arlostatic-z2.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:34 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:31 AM 192.168.0.64 registration.arloxcld.com
5/21/2022 11:50:31 AM 192.168.0.64 presence.arloxcld.com
5/21/2022 11:50:31 AM 192.168.0.64 registration.arloxcld.com
5/21/2022 11:50:31 AM 192.168.0.64 advisor.arloxcld.com
5/21/2022 11:50:31 AM 192.168.0.64 arlo-device.messaging.arlo.com
5/21/2022 11:50:31 AM 192.168.0.64 mcs.arlo.com
5/21/2022 11:50:30 AM 192.168.0.64 updates.arlo.com
5/21/2022 11:50:30 AM 192.168.0.64 updates.arlo.com
5/21/2022 11:50:30 AM 192.168.0.64 updates.arlo.com
5/21/2022 11:50:30 AM 192.168.0.64 mcs.arlo.com
5/21/2022 11:50:30 AM 192.168.0.64 mcs.arlo.com
5/21/2022 11:50:30 AM 192.168.0.64 updates.arlo.com
5/21/2022 11:50:30 AM 192.168.0.64 updates.arlo.com
5/21/2022 11:50:25 AM 192.168.0.64 xbroker-z2-i3.arloxcld.com
5/21/2022 11:50:25 AM 192.168.0.64 xbroker-z2-i3.arloxcld.com
5/21/2022 11:50:24 AM 192.168.0.64 advisor.arloxcld.com
5/21/2022 11:50:24 AM 192.168.0.64 advisor.arloxcld.com
5/21/2022 11:50:23 AM 192.168.0.64 registration.arloxcld.com
5/21/2022 11:50:22 AM 192.168.0.64 registration.arloxcld.com
5/21/2022 11:50:17 AM 192.168.0.64 time-b.netgear.com
5/21/2022 11:50:14 AM 192.168.0.64 updates.arlo.com
5/21/2022 11:50:09 AM 192.168.0.64 updates.arlo.com
5/21/2022 11:50:07 AM 192.168.0.64 time-b.netgear.com
5/21/2022 11:50:02 AM 192.168.0.6 oculus2883-us1.dropcam.com
5/21/2022 11:50:02 AM 192.168.0.6 oculus2883-us1.dropcam.com
5/21/2022 11:50:01 AM 192.168.0.6 nexus.dropcam.com
5/21/2022 11:50:01 AM 192.168.0.6 nexus.dropcam.com
5/21/2022 11:50:01 AM 192.168.0.6 nexus.dropcam.com

[ShayneS]

Are you still experiencing this issue? 

[mcho]

No but not because it got fixed.   I was desperate so I hauled out an old android pad I used until I found out how evil Google is a couple of years ago.   I was forced to sign into the google account I created for it, had to update android and then update Arlo.   Just out of sheer luck, I happened to remember the password to the Google account.  I was not happy about having to do this.  As an aside, on my desktop Linux machine, I specifically block all ranges of IP addresses that I know Google uses (and Apple and Microsoft as well).

At any rate, the android app quickly discovered and setup my Arlo equipment.  And then it began working again on my desktop.

The cause of initial problem is still unknown.   I use a great deal of security on my desktop, filtering packets using Wireshark, and I review scripts in the browser before allowing them to run and I use a multi-hop VPN (not Tor!) in addition to blocking evil players as mentioned.   But that could not be the cause because I tried to use a Windows machine with zero security other than native Windows 10 (essentially a virgin install) and had the identical issue.  I even opened my ports and shutdown my firewall on my router but that made no difference (Arlo previously worked just fine on the same router but you never know if Century Link made any changes).   The problem was almost certainly on the Arlo end.

If I had not happened to remember that I had an old android device I would have had a 400 dollar paperweight (unless I took the time to hack the cameras to run locally)  because apparently (official) support from Arlo is not to be had even though this was a problem clearly caused by Arlo.    Lesson learned I am actively looking to replace these cameras with generic PoE cameras that I can program myself and control locally.   As of this week I am learning how to program Home Assistant and will never buy commercial security cameras again.  

And no I do not use smart phones because I am an internet security expert and if you knew what I know you would not use them either.,