Support

Ruijie or Reyee Device Offline in Cloud

This guide addresses a Ruijie or Reyee gateway, switch or access point shows offline in cloud management in the order technical support would test it: preserve what matters, open the correct screen, correct the proven cause and verify the result.

Cloud Networking

Summary

Follow the four stages below to diagnose a Ruijie or Reyee gateway, switch or access point shows offline in cloud management without losing evidence, configuration or device ownership.

Applies to

  • Ruijie Cloud and Reyee-managed devices
  • Gateways, switches and wireless access points

Difficulty and time

Difficulty: Advanced

Estimated time: 25 to 60 minutes

What you will need

  • The exact model and current firmware or app version
  • Administrator access where authorised
  • A photo or screenshot of the current status
  • One controlled test case and its exact time

What this guide covers

  • Preserve and reproduce the fault
  • Open the correct diagnostic screen
  • Correct the proven cause
  • Verify and document the result

Use this page when a Ruijie or Reyee gateway, switch or access point shows offline in cloud management. It includes the menu or screen to look for, the status that matters and a repeatable proof test.

Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.

Before you start

Protect the current system and record a baseline before changing anything.

  • Write down the exact symptom: the device is locally powered but cloud status is Offline, or it has disappeared from the expected project.
  • Photograph the current status, error text, wiring or timeline as applicable.
  • Record the last known working time and anything changed immediately before the fault.
  • Export configuration and record project ownership before removing or resetting the device.
Important

Do not factory-reset a managed network device as the first step

A reset can remove VLAN, gateway, wireless and management settings and may interrupt CCTV or access-control traffic.

If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.

What usually causes this

  • Uplink or upstream internet is down
  • Gateway/DNS is invalid
  • Management VLAN is wrong
  • Device belongs to another project/account

Step 1: Preserve the current state and reproduce the fault

Begin with a repeatable baseline so you know whether a later change genuinely helped.

  • Reproduce the problem once and record: the device is locally powered but cloud status is Offline, or it has disappeared from the expected project.
  • Note whether every device or user is affected, or only one.
  • Compare one working path with the failing path if a comparison exists.
  • Export configuration and record project ownership before removing or resetting the device.

Step 2: Open the correct screen and inspect the evidence

The primary diagnostic location is Ruijie Cloud/Reyee app > Project > Device List > select device > Status/Diagnostics. Do not change anything until the displayed state is recorded.

  • Open Ruijie Cloud/Reyee app > Project > Device List > select device > Status/Diagnostics. Menu wording can vary by model and firmware; use the nearest equivalent label.
  • Check power, uplink and port LEDs at the device.
  • Confirm the device receives a valid IP, gateway and DNS and can reach the internet.
  • Verify serial/MAC identity and that the correct project/account owns it.

Step 3: Correct only the cause you proved

Use the matching correction below. Make one change, save it, then repeat the same test.

  • Restore the physical uplink and upstream internet path.
  • Correct DHCP, gateway, DNS or VLAN assignment for the management network.
  • Move/claim the device only through the authorised ownership workflow.
  • Upgrade firmware only after stable local and cloud connectivity is restored.

Step 4: Verify, monitor and document the handover

A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.

  • Confirm cloud status changes to Online and remains stable.
  • Open device details and check configuration synchronisation time.
  • Test a client through the affected network path.
  • Restart the upstream path in a planned window and confirm recovery.
Worked example

Controlled support test

Situation: The reported symptom was: the device is locally powered but cloud status is Offline, or it has disappeared from the expected project.

Solution used: The current state was recorded in Ruijie Cloud/Reyee app > Project > Device List > select device > Status/Diagnostics, one matching correction was made, and the same test was repeated.

Why this was chosen: This separated the proven cause from unrelated settings.

Installation notes: The final screenshot and test time were saved with the handover record.

Official reference used for this guide

Menu names differ between releases. Confirm model-specific behaviour in Ruijie Community Official Offline Troubleshooting before firmware, reset, storage or security-sensitive work.

Common mistakes

  • Changing several settings before repeating the original test.
  • Using a factory reset, initialise or format option as an early troubleshooting step.
  • Treating an app symptom as proof that the local hardware or recording has failed.
  • Failing to record the model, version, exact error and test time before escalation.
  • Assuming similar-looking models use identical menus or features.

Troubleshooting table

Symptom What to check What to do next
the device is locally powered but cloud status is Offline, or it has disappeared from the expected project power/uplink fault, invalid gateway/DNS, wrong management VLAN, project ownership or cloud reachability Open the named diagnostic screen, record the displayed state and use the matching correction above.
The named menu is not visible Different firmware, permissions or model capability Do not substitute a destructive menu. Capture the model and version and use its official manual.
The change saves but the fault remains The selected cause was not the root cause Undo the change if appropriate, return to the baseline and compare the failing path with a working one.
Local test works but app or client test fails Account, permission, cloud or remote-network path Keep the proven local configuration and diagnose the remote path separately.
Problem returns later Intermittent power, cable, storage, network or schedule condition Record the new failure time and status; correlate it with logs, events and the last known working interval.

When to contact support

Contact SecurityWholesalers support when local management and internet reachability are proven but the correctly owned device remains cloud-offline.

Send the order number if available, exact model, firmware or app version, screenshot of Ruijie Cloud/Reyee app > Project > Device List > select device > Status/Diagnostics, the failure time, and the result of the local proof test.

Related support guides

Related buying guides

Relevant product categories

Still stuck?

Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.

Frequently asked questions

  • Where should I click first for Ruijie device offline cloud?

    Start at Ruijie Cloud/Reyee app > Project > Device List > select device > Status/Diagnostics. Record the existing state before changing it because labels and available options can vary by model and firmware.

  • What should I look for on that screen?

    Look for last-online time, management IP/gateway/DNS, uplink state, serial/MAC and project/account ownership.

  • What must I avoid changing during the first check?

    A reset can remove VLAN, gateway, wireless and management settings and may interrupt CCTV or access-control traffic.

  • How do I prove the correction worked?

    Hold stable Online/synchronised status and pass a real client test through the device after a planned restart.

  • Why might my menu names look different?

    Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.

  • Should I factory-reset the device?

    Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.

  • What should I send technical support?

    Send the exact model and version, screenshot of Ruijie Cloud/Reyee app > Project > Device List > select device > Status/Diagnostics, exact error text, failure time, what changed before the fault and the result of the controlled local test.

  • Can configuration changes recover data or events that were never recorded?

    No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.

Further Reading
Guide Page Security Network Support Guides Overview Overview Guide Page Hikvision Support Guides Guide Page HiLook Support Guides

We make product support and ordering easy! Reach out to our help team :)
Trade Customers: Log In or Register to Unlock Even Better Prices.

Save & Share Cart
Your Shopping Cart will be saved and you'll be given a link. You, or anyone with the link, can use it to retrieve your Cart at any time.
Save Cart & Generate Link
Send Cart in an Email Done! close
Empty cart. Please add products before saving :)

Back Save & Share Cart
Your Shopping Cart will be saved with Product pictures and information, and Cart Totals. Then send it to yourself, or a friend, with a link to retrieve it at any time.
Send Cart Email
Your cart email sent successfully :)