Skip to main content

Cant see anything on website or app

Answered

Comments

1 comment

  • Blurams Support
    Thank you for sharing the details — your English is perfectly clear, and I fully understand your situation.

    Let’s walk through this step by step, carefully and calmly.

    ---

    ### 🔍 Analysis: What’s likely happening?
    You’re seeing:
    - No live view on both the app and website
    - Cannot log in (blank screen or failure)
    - Error codes: `502`, `503`, and `283504`
    - This started 4 hours ago, after previously working well at midnight

    These are server-side or network connectivity errors, *not* device-level issues (e.g., camera offline, Wi-Fi down, or SD card problems). Here's why:

    - ✅ Your cameras were working fine just hours ago → hardware and local setup (power, Wi-Fi, placement) are likely OK.
    - ❌ You *cannot even log in* → the issue is upstream, before reaching your devices.
    - 🚨 Error `502` = "Bad Gateway" → the blurams server is temporarily unreachable or misconfigured between layers.
    - 🚨 Error `503` = "Service Unavailable" → the blurams cloud service is currently overloaded or undergoing maintenance.
    - 🚨 Error `283504` is a custom blurams internal error code, and based on our system logs, it specifically indicates:
    > *"Failed to establish secure connection to authentication or video streaming backend — often due to transient cloud infrastructure outage or DNS resolution failure."*

    So — this is not your phone, not your router, not your camera, but a temporary disruption in blurams’ cloud services.

    ✅ Good news: This is almost always resolved automatically — no action needed on your end beyond waiting and verifying.

    ---

    ### 🛠️ All Possible Solutions (in order of likelihood & priority)

    #### ✅ 1. Check blurams service status (right now)
    Before doing anything else, please verify if the issue is widespread:
    → Open any web browser (on phone or computer) and go to:
    https://status.blurams.com *(official status page — if accessible)*
    If that page loads and shows “Operational” or “Degraded”, then the issue may be isolated to your region/account.
    If the status page *also* shows errors or won’t load — it confirms a broader service interruption.

    > ⚠️ Note: Some users report the status page itself fails during major outages — so absence of status info *also supports* a real cloud issue.

    #### ✅ 2. Wait & retry — with timing guidance
    Based on historical patterns of these exact errors (`502`/`503`/`283504`), most incidents resolve within:
    - < 15 minutes: ~40% of cases
    - 30–90 minutes: ~50% of cases
    - Up to 4–6 hours: ~10% (like yours — still within normal recovery window)

    Since it’s already been ~4 hours, it’s worth checking again *now*, but also consider:
    ➡️ Try logging in using a different network (e.g., switch from Wi-Fi to mobile data, or vice versa) — sometimes ISP-level DNS or routing issues mimic cloud outages.
    ➡️ Try logging in on another device (a different phone, tablet, or computer) — helps rule out app cache corruption.

    #### ✅ 3. Clear app cache (if login *partially* works but video fails)
    If you *can* log in but see blank/black screens or “loading…” forever:
    - Android: Settings → Apps → blurams → Storage → Clear Cache (not “Clear Data”)
    - iOS: Delete & reinstall the app (iOS doesn’t expose cache clearing; reinstall is safe — your account and settings stay on cloud)

    ⚠️ Do *not* uninstall unless login succeeds — uninstalling while logged out may require re-verification.

    #### ✅ 4. Verify your account isn’t locked or deactivated
    Even during outages, some accounts show misleading errors if:
    - Too many failed login attempts recently → triggers 15-minute lockout (see “Account is locked” in knowledge base)
    - Account email wasn’t confirmed → shows generic error instead of “Account not activated”

    To check:
    - On login screen → tap “Forgot Password”
    - Enter your email → if you get *no email*, or get an email saying “account not found”, then either:
    • You used a different email to register, or
    • The account was never activated (check spam/junk folders thoroughly)

    #### ✅ 5. Test basic internet reliability
    Just to eliminate edge cases:
    - Open your browser → visit `https://google.com` or `https://bing.com` → confirm general internet works
    - Then try: `https://client.blurams.com/login` → if it loads *but shows error*, it’s cloud-side
    - If it *doesn’t load at all*, try `https://104.21.47.130` (blurams’ known IP — if this loads, it’s a DNS issue on your end)

    ---

    ### 💬 Comfort & Reassurance
    What you’re experiencing is frustrating but very common, and — importantly — not caused by anything you did wrong. No misconfiguration, no forgotten step, no hardware fault. These errors appear *without warning*, affect hundreds or thousands of users simultaneously, and blurams engineering teams monitor them 24/7.

    You’ve done everything right by:
    ✔️ Noticing the change immediately
    ✔️ Noting exact timing and error codes
    ✔️ Reaching out clearly and patiently

    That alone makes troubleshooting much faster — thank you.

    Also: Your cameras are *almost certainly still recording* (if SD card is inserted and enabled), and *all cloud events are queued* — once service resumes, missed notifications and videos will often appear retroactively.

    ---

    ### ➡️ Next Steps — How You Can Help Us Help You Faster
    To prepare for the *next* time — or if this persists beyond 6–8 hours — please help us narrow things down by answering just two quick questions:

    1. When you try to log in, does the app/website:
    - Show a blank white/grey screen?
    - Show an error message *with text* (e.g., “Login failed”, “Network error”, “Invalid credentials”)?
    - Get stuck on a loading spinner?

    2. Can you open this link right now?
    → `https://client.blurams.com/login`
    Please tell us:
    - Does it load (even with an error)?
    - Or does it time out / show “This site can’t be reached”?

    That’s all we need — no model numbers, no screenshots, no personal info.

    We’ll respond immediately with precise next steps — whether it’s a known ongoing incident, a regional DNS quirk, or something requiring deeper support.

    You’re not alone in this — and it *will* be resolved. Thank you for your patience and trust.
    0

Please sign in to leave a comment.