360Eyes App Stuck on "Connecting to Server" or TCP Connection Failure

When the 360Eyes app shows "connecting to server" indefinitely, or an error like "TCP connection failure", it means your phone cannot complete a connection to the vendor's cloud servers. The quick test: switch your phone from WiFi to mobile data and reopen the app. If it connects on mobile data, the problem is your network. If it fails on both, the problem is most likely on the server side — and waiting is usually the only fix.

This error is about the link between your phone and the cloud, not between the camera and your router. Your camera may be perfectly online while the app still can't log in.

What the "connecting to server" error means

The 360Eyes app talks to cloud servers for login, the Devices list, push alerts, and remote live view. "Connecting to server" appears while that handshake is in progress; a TCP connection failure means the handshake was attempted and actively failed. Either way, there are only three places the problem can live:

1. Your phone — airplane mode, VPN, stale app data, outdated app.
2. Your network — WiFi without working internet, firewall, DNS issues, restrictive networks (hotel, office, school).
3. The vendor's servers — outages or maintenance. Less common, but it happens, and when it does the error hits all users at once.

Network problem or server-side outage? Two quick tests

1. Switch networks. Turn off WiFi and use mobile data (or vice versa). Works on one but not the other → the failing network is the culprit.
2. Check the pattern. If other apps and websites work fine on the same phone, but 360Eyes fails on every network you try — and especially if other users report the same thing at the same time — it points to a server-side outage. Outages typically resolve on their own within hours.

Fix checklist for the 360Eyes "connecting to server" error

Work through these in order; stop when the app connects.

1. Restart the app. Force-close it completely and reopen. A stale session is the cheapest possible fix.
2. Restart your phone. Clears DNS caches and broken network state.
3. Toggle networks. WiFi off → mobile data, or join a different WiFi network, to localize the failure.
4. Disable VPN, proxy, and private DNS. VPNs and ad-blocking DNS services are a frequent cause of TCP connection failures because they can block or reroute the app's server endpoints. Turn them off, then retry.
5. Reboot your router. If the failure only happens on your home WiFi, power cycle the router and confirm general internet access works on the same network.
6. Update the app. Old versions can point at retired server endpoints. Get the latest from the App Store (iOS) or Google Play (Android).
7. Clear the app's cache (Android) or reinstall (iOS). On Android, clearing storage for 360Eyes Pro removes corrupted local data; on iOS, delete and reinstall the app. You'll need to log in again, so make sure you know your account password first.
8. Check date and time settings. A phone clock that's significantly wrong can break secure connections. Set date and time to automatic.
9. Try a restrictive-network workaround. Corporate, school, and hotel networks often block the ports or protocols the app needs. Test on mobile data or a home network; if it works there, the restrictive network is the cause and only its administrator can fix it.
10. Wait it out. If everything above fails on every network, treat it as a server-side issue. Retry after a few hours rather than resetting your camera — a reset won't help when the servers are down.

Edge cases

• Error only during login or signup: server-side and region issues are more likely; retry later before assuming your account is broken.
• Devices list loads but live view fails: that's usually a camera-side or bandwidth problem, not a server one — see camera offline fixes.
• Error appears only when away from home: your camera's upload bandwidth or your remote network may be the limit, not the servers.
• Running the app in BlueStacks or another Android emulator: emulator networking adds another failure layer; verify the same account works on a real phone before debugging further.
• Brand-new setup that has never connected: the problem may actually be pairing, not the server — see camera not connecting to WiFi.