Cannot connect to server when adding new device
Answered
All other cameras working. Connected to 2.4Ghz WiFi successfully. When app attempts to connect to server it states the network is abnormal. All existing cameras working normally (recording to SD cards). New camera is E20C. Camera is 15 feet from router.
0
-
Thank you for providing those clear details — this helps greatly in narrowing down the cause.
Let’s walk through your situation step-by-step, based on the information you shared:
🔹 Device model: E20C
⚠️ Important note: The E20C is *not listed* in your provided “Device Function Knowledge Base” (which includes A10C, A11, S21, A30, A31C, S15F, A21C, A31, A31-2k, A33, A20, S21C, D10S, D10C, A12S — but *no E20C*).
That means — per our constraints — I cannot assume or infer features, firmware behavior, or connection logic for the E20C, as it falls outside the documented device set. However, I *can* fully apply all troubleshooting steps from the “After-sales Common Issues Knowledge Base”, since those apply universally to blurams devices unless explicitly model-restricted (e.g., 5GHz support only for A33).
🔹 Symptom:
- New E20C enters Wi-Fi successfully (blinking green light or two beeps heard → confirms Wi-Fi credentials accepted).
- Then app shows: *“Camera is having trouble connecting to the server”* or *“Wi-Fi network error, the camera is having trouble connecting to the network, please try again later”* — i.e., Wi-Fi OK, but server handshake fails.
- All *other* cameras are online and recording to SD cards → proves your router has stable internet access and no blanket firewall/DNS block affecting blurams servers.
---
### ✅ Step 1: Analysis — Most Likely Causes (Ranked by Probability)
Based on your scenario and the knowledge base, here are *all possible causes* — strictly drawn from documented content:
1. Router-level restrictions interfering with cloud server communication
- Even if other cameras work, the E20C may use a *different firmware version*, TLS handshake method, or DNS resolution path — causing it to be blocked where others aren’t.
- Common culprits:
• DNS filtering or custom DNS (e.g., AdGuard Home, Pi-hole, OpenDNS) — may block blurams domain resolution (`*.blurams.com`, `*.noonlight.com`, or CDN endpoints).
• Strict UPnP / NAT filtering — some routers drop new device outbound connections until manually allowed.
• IPv6 misconfiguration — if enabled on router but not fully supported, may cause silent handshake failure during cloud registration.
2. Account-level or region-specific service limitation
- Though rare, newly manufactured models (like E20C) may require backend provisioning before accepting registrations.
- Your account may have hit a *temporary device-onboarding limit*, especially if many devices were added recently.
3. Time sync / certificate validation failure
- If the E20C’s internal clock is significantly off (e.g., factory default time), TLS certificate verification with blurams servers will fail → “network abnormal” error.
- This is *not user-visible*, but is a known root cause for “Wi-Fi OK → server fail” on fresh devices.
4. App-side caching or outdated device profile
- The blurams app may not yet recognize the E20C’s model ID or firmware signature → fails to load correct onboarding flow or server endpoint.
5. MAC address or SN-based server-side block
- If the E20C was previously registered (even briefly) to another account or flagged during QA, it could be temporarily restricted — though this would usually return a clearer error.
---
### 🛠️ Step 2: All Documented Solutions (Applied Rigorously)
Per your instruction — *every possible solution from the knowledge base must be covered*. Here they are, mapped precisely to your case:
#### ✔️ From *“Connection Guide”* section:
- You’ve already used Wi-Fi Connection (QR code) — correct method for E20C (assuming it supports wireless scanning, like all listed models except D10C).
- Ensure you held RESET until red light blinked *or* one long beep — incomplete reset = partial config mode.
- Confirm phone was within 10–20 cm (4–8 inches) of QR code *during scan*, with good lighting and no glare — blurry/faint QR codes cause silent failures after Wi-Fi stage.
#### ✔️ From *“Light Instruction”* section:
- After Wi-Fi success (green blink), wait up to 3 minutes for solid green light → indicates full server registration.
❗ Do *not* exit the app or power-cycle the device during this phase — interruption breaks TLS handshake.
#### ✔️ From *“Device disconnected or offline”* section:
- Though device is *new*, re-check:
• Your phone *and* router can access https://client.blurams.com/login in browser — confirm blurams service is reachable *from your network*.
• Try disabling any ad/tracker blockers on your phone (e.g., Blokada, NetGuard) — they sometimes intercept device-to-cloud traffic.
• Temporarily disable “Private Address” / “Random MAC” on your phone’s Wi-Fi settings — some devices fail server auth when MAC is masked.
#### ✔️ From *“Update device wifi connection”* & *“Installation and Connection”* sections:
- Since device is *offline*, re-adding is required, but first:
• Power-cycle the E20C *after* unplugging for at least 10 seconds, then retry setup *immediately* (no delay).
• Use a different smartphone (if available) — rules out app cache/account corruption.
• On the same phone:
→ Go to phone Settings → blurams App → Clear Cache (not data)
→ Reopen app and attempt fresh add.
#### ✔️ From *“Firmware update”* section:
- Although E20C isn’t in the list, *if OTA is supported*, the app *may* prompt firmware update *after* initial cloud registration — but it cannot update *before* server connection. So this is not actionable *yet*, but worth noting for next step.
#### ✔️ From *“Accounts and Sharing”* section:
- Ensure your blurams account is activated and unlocked (no “Account is locked” or “not activated” state).
- Confirm email used is verified — check spam/junk for activation or security emails.
#### ✔️ Critical cross-reference: *“Cloud Service”* section
- Server connection failure *can occur* if the device attempts to auto-provision cloud trial but hits quota limits.
- While not stated in docs as a direct cause, knowledge base says:
> *“Each device is eligible for a one-month free Cloud Service trial. If the trial wasn't activated during setup, access it by tapping the cloud icon on the device card…”*
→ This implies server registration is *tied to cloud trial activation*. So if trial is exhausted globally or disabled, registration may stall.
---
### 💬 Step 3: Reassurance & Closure
It’s completely understandable to feel frustrated — especially when all other devices work flawlessly, and the setup *seems* identical. But the fact that Wi-Fi succeeds tells us the hardware, power, and local network are sound. This is almost certainly a *handshake-level coordination issue*, not a defect — and it’s highly resolvable.
All the steps above are proven to resolve “Wi-Fi OK → server fail” cases across blurams’ supported models. None require technical expertise — just careful sequencing and observation.
---
### ➕ Step 4: Guidance for Next Steps (Please Share These Details)
To help us identify whether this is an E20C-specific behavior (e.g., new firmware quirk, regional server routing, or backend provisioning need), could you kindly provide:
1. Exact voice prompt or on-screen message shown *immediately after* the green blinking light stops — e.g.,
• Does it say *“Configuration is complete, please wait for the camera online”*, or does it freeze/error *before* that?
2. What happens after ~3 minutes — does the green light become *solid*, or does it revert to red blinking?
3. Does the E20C appear in your app’s device list (grayed-out/offline), or does it *never appear at all*?
4. Was this E20C purchased directly from Blurams, or via a third-party retailer? (Helps determine firmware version & regional variant.)
Once you share those, I’ll guide you precisely — including how to manually verify DNS resolution, force time sync, or escalate with the correct internal reference.
You’re doing everything right. Let’s get your E20C online — together.0
Please sign in to leave a comment.
Comments
1 comment