Troubleshooting

ALPON · Sixfab Connect Platform

Use this guide to diagnose and resolve issues with the Sixfab Connect platform and ALPON software. Start with general checks, then move to service-specific diagnostics.

General Troubleshooting Guide

If you encounter any issues while using the Sixfab Connect platform, work through the following steps in order:

Verify Browser Compatibility

Ensure you are using a supported browser (Chrome, Firefox, Edge, Safari) updated to the latest version. Clearing the cache and cookies, or switching to an incognito window, can often resolve minor issues.

Reproduce the Issue

Attempt to replicate the problem to identify the actions leading up to it. Note whether the issue is consistent or intermittent.

If intermittent, record the frequency and duration — for example: does it happen on a specific day, or only after 5pm? When working with intermittent problems, always look for patterns using a standardized approach.

Network and Connection Check

Verify your internet connection is stable. If the issue involves device connectivity, ensure the device is online and registered correctly in the platform.

Check Platform Status

Check if the Sixfab Connect platform is undergoing maintenance or updates. This information is typically found in announcements or status pages.

Troubleshooting ALPON Software Issues

Follow these diagnostic methods to identify and resolve issues related to ALPON software operation.

Diagnostic Commands

Monitor K3S System Pods

Run the following command to check the status of core system pods:

kubectl get pods -n kube-system

A healthy system shows all pods with Status: Running and Ready: 1/1:

NAME                                      READY   STATUS    RESTARTS       AGE
coredns-5dd589bf46-dv67r                  1/1     Running   28 (72m ago)   21d
local-path-provisioner-846b9dcb6c-l9jt2   1/1     Running   28 (72m ago)   21d
metrics-server-5dc58b587c-tdlps           1/1     Running   28 (72m ago)   21d

⚠️

Error States If STATUS shows CrashLoopBackOff, Pending, or Unknown, this indicates an error. An Unknown state may indicate K3S cannot recover its own system pods — a common cause is sudden power loss to the device.

Monitor Sixfab Namespace Pods

kubectl get pods -n sixfab

A healthy output shows all pods as Running and 1/1:

NAME                               READY   STATUS    RESTARTS       AGE
agent-54b857fdf8-sqccr             1/1     Running   30 (67m ago)   20d
device-manager-5778f45fdc-sp9j7    1/1     Running   28 (67m ago)   20d
geolocation-859b7ddf6c-dd4bl       1/1     Running   28 (67m ago)   20d
modem-manager-6bf58df8dd-mtx2j     1/1     Running   1 (67m ago)    2d16h
network-manager-6594ffbd9d-9n4qw   1/1     Running   28 (67m ago)   20d

If any pod shows an error state, inspect it further:

Pod Details

kubectl -nsixfab describe pods <POD_NAME>

Replace <POD_NAME> with the name of the problematic pod from the previous command.

Pod Logs

kubectl -nsixfab logs -f -l app=<APP_NAME>

Replace <APP_NAME> with one of: agent, modem-manager, network-manager, device-manager, or geolocation.

System Services

1. Supervisor Service

Check the Supervisor — the main system service of the ALPON software:

sudo systemctl status alpon_supervisor.service

A healthy status shows active (running):

● alpon_supervisor.service - Sixfab Alpon Supervisor
     Loaded: loaded (/etc/systemd/system/alpon_supervisor.service; enabled; preset: enabled)
     Active: active (running) since Mon 2024-10-21 06:58:43 EDT; 1h 45min ago
   Main PID: 558 (sudo)
      Tasks: 11 (limit: 8731)
     Memory: 71.4M
        CPU: 17.404s

View live logs:

sudo journalctl -fu alpon_supervisor

In a healthy idle state, the following repeating log pattern is expected:

Oct 21 08:49:53 alpon sudo[594]: time=2024-10-21T08:49:53.457 level=DEBUG msg="Control loop started"
Oct 21 08:49:56 alpon sudo[594]: time=2024-10-21T08:49:56.411 level=DEBUG msg="Control loop finished"
Oct 21 08:50:49 alpon sudo[594]: time=2024-10-21T08:50:49.343 level=DEBUG msg="After last handshake, passed"

2. Remote Terminal Service

If there is an issue with the Remote Terminal, check the Terminal service:

sudo systemctl status alpon_terminal.service

● alpon_terminal.service - Sixfab Alpon Terminal
     Loaded: loaded (/etc/systemd/system/alpon_terminal.service; enabled; preset: enabled)
     Active: active (running) since Mon 2024-10-21 06:58:43 EDT; 1h 48min ago
   Main PID: 559 (sudo)
      Tasks: 8 (limit: 8731)
     Memory: 37.8M
        CPU: 662ms

View live logs:

sudo journalctl -fu alpon_terminal

Common Issues and Solutions

Possible Causes

Device not activated on the Sixfab Connect platform.
Data limit may have been reached.

Diagnostic Command

Check modem-manager logs for result=false or Error entries.

kubectl -n sixfab logs -f -l app=modem-manager

Steps to Resolve

The device may not be able to reach the internet. Use Ethernet or Wi-Fi to bring it online and verify if this resolves the issue. If it does, check the modem-manager logs.
If online but still inactive, the device may not have received its key and token information. Check the Supervisor logs and verify the definitions.yaml file.

sudo journalctl -fu alpon_supervisor

cat /home/sixfab/apps/definitions.yaml

The peer_details key must have values assigned. If the file is empty or missing values, contact the technical support team to confirm the device has been added to Sixfab records.

peer_details:
  token: ****************
  wg_endpoint: ndev.sixfab.com:51820
  wg_peer_ip: ***********
  wg_peer_allowed_ip: **********
  wg_server_public_key: **********************
  websock_endpoint: wss://ws.sixfab.io/ws
  registry_url: cr.sixfab.com

Possible Causes

Performing an update over a cellular network may cause high data consumption, potentially exceeding the data limit.

Steps to Resolve

Check the status and logs of the Supervisor service.
Verify that the cellular data limit has not been exceeded.

Possible Cause

If the Device Manager cannot feed the watchdog at regular intervals, the watchdog will restart the device.

Diagnostic Commands

Check whether the Device Manager pod is running.

kubectl get pods -n sixfab | grep agent

kubectl -n sixfab logs -f -l device-manager

Monitor Resource Usage

Use htop to monitor RAM usage of all running applications on the device.

htop

Software Service Reference

When a problem occurs, identifying which service is responsible helps narrow down the diagnosis. Each service owns a specific area of functionality:

Supervisor

Controls the overall ALPON software system
Updates systemd services and applications
Sets up the Sixfab Network (keys, peer details)
Handles app deployments and reboot requests

Agent

Maintains WebSocket connection with the platform
Transmits device data to the platform
Sends periodic heartbeat messages

Network Manager

Manages network interfaces and metric values
Modem (usb0) has lower priority than Wi-Fi/Ethernet by default
Configures new Wi-Fi interfaces via the platform

Modem Manager

Manages modem via AT commands
Ensures internet connectivity at device boot
Handles LPA operations for eSIM management
Controls the cellular status LED

Device Manager

Sends periodic signals to the watchdog chip
Manages LEDs, add-ons, ADC, buttons, I2C, TPM

Terminal

Provides remote terminal access through the platform.

Geolocation

Handles location services, sending device location to the platform via the Agent.

Hardware Issues

Possible Causes

Insufficient airflow around the device.
Operation in a high-temperature environment.

Solutions

Place the device in a well-ventilated area and ensure airflow is not obstructed.
Avoid operating in environments exceeding the recommended temperature limits.

Possible Causes

Incorrect network configuration.
Weak or unstable network signal.
Improperly connected antennas.

Solutions

Verify network settings in the Sixfab Connect platform.
Check signal strength and reposition antennas if needed.
Confirm that GNSS, Wi-Fi, and LTE antennas are securely connected and unobstructed.

Possible Causes

Power adapter not properly connected.
Insufficient power supply.

Solutions

Make sure the power adapter is securely connected to the device.
Test the adapter with another compatible device to verify it is functioning.
We recommend using the power adapter included in the box.
Ensure the power supply meets the required specification — minimum 27W. If using USB-C PD or PoE, confirm sufficient power output.

Reporting an Issue

If troubleshooting does not resolve the issue, gather the following information before contacting Support:

Screenshots or Recordings — Capture the issue, including error messages or unexpected behaviors.
Browser and OS Details — Note the browser name, version, and operating system in use.
Developer Console Logs — Open the browser console (Ctrl+Shift+I or Cmd+Option+I) and copy any error messages.
Steps to Reproduce — A clear, numbered description of the actions that trigger the issue.

Ready to contact Support?

Include the information above to help us resolve your issue faster.

Contact Support →