Applies to: RockREMOTE Mini in its complete enclosure. Not Mini OEM, RockREMOTE Classic or Rugged. Match hardware and firmware with the installation record.
Match your symptom
| What you see | What to do next |
|---|---|
| Check the actual local network | Privately record the label, firmware, actual LAN address, client address and subnet, connection method, exact status, application destination and time. Capture whether the failure began after a configuration upload or equipment replacement. Share logs only with authorized support; redact credentials and identifiers from public screenshots. |
| Record service state before application tests | Use an authorized existing installation. Do not open the enclosure, disconnect live antenna wiring, replace firmware or reset a commissioned system merely to test it. Ask the network owner to control laptop background traffic before connecting; default outbound access can consume satellite data. Do not remove firewall protections as a general repair step. |
| Preserve the uploaded configuration | Privately record the label, firmware, actual LAN address, client address and subnet, connection method, exact status, application destination and time. Capture whether the failure began after a configuration upload or equipment replacement. Share logs only with authorized support; redact credentials and identifiers from public screenshots. |
| Request the right log evidence | Use an authorized existing installation. Do not open the enclosure, disconnect live antenna wiring, replace firmware or reset a commissioned system merely to test it. Ask the network owner to control laptop background traffic before connecting; default outbound access can consume satellite data. Do not remove firewall protections as a general repair step. |
Work through these checks
Check the actual local network
Documented default: 192.168.250.1; DHCP disabled. Compare installed values with the client’s address rather than overwriting them. Ask the administrator to resolve subnet or duplicate-address issues; preserve the working network configuration while narrowing the fault.
What the result means: Privately record the label, firmware, actual LAN address, client address and subnet, connection method, exact status, application destination and time. Capture whether the failure began after a configuration upload or equipment replacement. Share logs only with authorized support; redact credentials and identifiers from public screenshots.
Record service state before application tests
Read PPP Status and Provisioning from the existing local interface. Save the exact text, then distinguish the service state from the destination’s failure. Do not keep sending internet probes or retrying a payload without the owner’s test plan and data allowance.
What the result means: Use an authorized existing installation. Do not open the enclosure, disconnect live antenna wiring, replace firmware or reset a commissioned system merely to test it. Ask the network owner to control laptop background traffic before connecting; default outbound access can consume satellite data. Do not remove firewall protections as a general repair step.
Preserve the uploaded configuration
The OEM warns that invalid user.cfg JSON can fall back to defaults without an error. If trouble followed an upload, keep both the intended file and a readback for support to compare. Do not conclude that accepting a transfer proves the settings were applied, and do not repeatedly upload modified copies without a controlled rollback plan.
What the result means: Privately record the label, firmware, actual LAN address, client address and subnet, connection method, exact status, application destination and time. Capture whether the failure began after a configuration upload or equipment replacement. Share logs only with authorized support; redact credentials and identifiers from public screenshots.
Request the right log evidence
Firmware v0.15 onward: appLog.log persists across reboots; local retrieval requires LAN and TFTP. Give support the installed version before attempting retrieval. If access is disabled, ask for the approved collection method rather than opening services indiscriminately. Preserve the original file and failure time so support can correlate events; remote collection uses data.
What the result means: Use an authorized existing installation. Do not open the enclosure, disconnect live antenna wiring, replace firmware or reset a commissioned system merely to test it. Ask the network owner to control laptop background traffic before connecting; default outbound access can consume satellite data. Do not remove firewall protections as a general repair step.
When to stop and get help
Use an authorized existing installation. Do not open the enclosure, disconnect live antenna wiring, replace firmware or reset a commissioned system merely to test it. Ask the network owner to control laptop background traffic before connecting; default outbound access can consume satellite data. Do not remove firewall protections as a general repair step.
What to tell support
Privately record the label, firmware, actual LAN address, client address and subnet, connection method, exact status, application destination and time. Capture whether the failure began after a configuration upload or equipment replacement. Share logs only with authorized support; redact credentials and identifiers from public screenshots.
Original troubleshooting guidance based on the official sources below. Menu names can change. This is an independent guide, not a manufacturer service bulletin or a bench-tested repair.