RUFUS Help
RUFUS CloudBox
RUFUS CloudBox
  • Introduction to RUFUS CloudBox
  • GETTING STARTED
    • Getting Started with RFID Technology
    • Introduction to Race Timing
    • RFID for Race Timing
    • Networks 101: Understanding the Basics for Race Timing
    • CloudBox Ports & Characteristics
  • PROTOCOL
    • How to Connect to the CloudBox
    • Protocol Commands and Responses
    • Receiving Timing Data Passings During a Session
  • CONNECTIONS
    • Connecting to the CloudBox: LAN, WiFi, and 4G Overview
    • Connecting the CloudBox via Ethernet Cable
    • Connecting the CloudBox via WiFi Access Point
    • Connecting the CloudBox to an External WiFi Network
    • Connecting Two or More CloudBox in the Same Network via a Hub or Router
    • Connecting the CloudBox to a 4G Network
  • Interface
    • Accessing the CloudBox Interface: General Guide
    • Timing Interface
    • Status Interface
    • Configuration Interface
    • Backup Interface
    • GPS Interface
    • Cloud Interface
  • General Operations
    • RFID Reader Configuration
    • RFID Reader Installation
    • Knowing your CloudBox IP Address
    • Boot Sequence
    • Starting and Stopping a Timing Session
    • Accessing Backup Files on the CloudBox
    • Time Synchronization Methods
    • LED Signals and Alarm Notifications
    • Connecting your CloudBox with RUFUS Race Manager (locally)
    • Connecting your CloudBox with Wiclax (locally)
  • ADVANCED OPERATIONS
    • Firmware Update
    • Network Configuration
    • GPS Service
    • Backup Rewind Function
    • IoT Service
    • 4G Modem
  • Cloud
    • Introduction to CloudBox Cloud Service
    • Binding the CloudBox with the RUFUS Cloud Service
    • Accessing Stored Cloud Timing Sessions
    • Connecting your CloudBox with RUFUS Race Manager (remote)
  • Care and maintenance
    • Warning!
    • Battery Care
    • Taking Care of your CloudBox
    • General Recommendations
    • Special Note on UHF Cables
  • Common problems
    • FAQ
    • Common Problems and Troubleshooting
Powered by GitBook
On this page
  • Connecting to the CloudBox Interface
  • Accessing the Interface When Multiple CloudBox Devices Are in the Same Network
  • Important Considerations
  • Summary
  1. Interface

Accessing the CloudBox Interface: General Guide

The CloudBox interface is a web-based dashboard that allows you to manage and monitor your timing system. This interface is accessible via a web browser, whether you’re connected to the CloudBox over Ethernet or WiFi. From the dashboard, you can view and control various aspects of the system, including timing data, network settings, and more.

In this article, we’ll walk you through how to access the CloudBox interface and what to consider when using multiple CloudBox devices on the same network.

Connecting to the CloudBox Interface

To access the CloudBox interface, you can connect either via Ethernet or WiFi:

1. Connecting via Ethernet

  • Connect your computer directly to the CloudBox using an Ethernet cable.

  • Once connected, open a web browser and navigate to one of the following:

    • cloudbox.local (if only one CloudBox is on the network).

    • The IP address of the CloudBox (e.g., http://192.168.1.10).

2. Connecting via WiFi Access Point

  • Connect your computer or device to the WiFi Access Point generated by the CloudBox (e.g., CLBX_192_168_1_10).

  • Once connected, open a web browser and navigate to:

    • cloudbox.local (for single CloudBox setups).

    • The IP address of the CloudBox (e.g., http://192.168.4.2 if connected to the WiFi Access Point or http://192.168.1.10).

Accessing the Interface When Multiple CloudBox Devices Are in the Same Network

If you are working with multiple CloudBox devices on the same network, accessing the interface becomes more specific. Here’s what you need to consider:

  1. cloudbox.local Conflict:

    • When multiple CloudBox devices are connected to the same network, the cloudbox.local address will no longer uniquely identify a single device. The same hostname will be shared among all connected CloudBox units, causing conflicts in accessing the dashboard.

  2. Mandatory Access via IP Address:

    • To avoid this conflict, you will need to access each CloudBox by its IP address rather than using cloudbox.local. Each CloudBox should be configured with a unique IP address, allowing you to distinguish between devices.

    • For example:

      • CloudBox 1: http://192.168.1.10

      • CloudBox 2: http://192.168.1.11

      • CloudBox 3: http://192.168.1.12

Important Considerations

  1. Unique IP Addresses:

    • When working with multiple CloudBox devices, ensure each device is configured with a unique IP address on the network. This is necessary to avoid IP conflicts and ensure smooth communication across the network.

  2. Firewall/Antivirus Settings:

    • Make sure that any firewall or antivirus software on your computer is not blocking access to the CloudBox. Temporarily disabling such software can help in troubleshooting connection issues.

  3. Browser Compatibility:

    • The CloudBox interface works best with modern web browsers like Google Chrome, Mozilla Firefox, or Microsoft Edge. Ensure your browser is up-to-date for the best performance.

Summary

To access the CloudBox interface, connect via Ethernet or WiFi and navigate to cloudbox.local or the CloudBox’s IP address through a web browser. When working with multiple CloudBox devices on the same network, always access the devices through their unique IP addresses, as cloudbox.local will not differentiate between multiple units.

This interface allows you to configure settings, monitor timing data, and manage network configurations, ensuring you can efficiently control your timing system from a single location.

PreviousConnecting the CloudBox to a 4G NetworkNextTiming Interface

Last updated 8 months ago