Skip to main content

General

Gateway Issues

Troubleshoot Edge Gateway connection and communication problems.

Gateway Not Connecting

Symptoms

  • Gateway shows Disconnected status in the console
  • No data flowing from devices assigned to this gateway

Common Causes

Check Network Connectivity

Ensure the gateway machine can reach the Central Server:

# From the gateway machine
ping <central-server-ip>
curl http://<central-server-ip>:8080/health

Verify NATS Connection

The gateway connects to the Central Server via NATS. Check if NATS is reachable:

# Default NATS port is 4222
telnet <central-server-ip> 4222

Check Configuration

Verify Proxus-config.toml on the gateway (see Configuration Reference):

[Nats]
Url = "nats://<central-server-ip>:4222"

Review Gateway Logs

Check the gateway service logs:

# Docker deployment
docker logs proxus-edge-gateway

# Systemd deployment
journalctl -u proxus-gateway -f

Gateway Keeps Reconnecting

Symptoms

  • Gateway status flickers between Connected and Disconnected
  • Log shows: Cluster shutdown detected! Restarting service!!

Solutions

CauseSolution
Network instabilityCheck firewall rules, ensure ports 4222 (NATS) and 1883 (MQTT) are open
Memory pressureIncrease container memory limit or reduce device count
Central Server restartNormal behavior during maintenance; gateway will auto-reconnect

MQTT Broker Issues

Cannot Connect to Internal MQTT Broker

The gateway runs an internal MQTT broker for local device communication.

info
Default MQTT Port

Internal broker listens on port 1883 (TCP) and 9001 (WebSocket).

Check broker status:

# Verify MQTT port is listening
netstat -an | grep 1883

Error: "Max reconnect attempts reached"

This appears in logs as:

Max reconnect attempts reached. Please check the MQTT broker.

Solutions:

  1. Verify the MQTT broker address in device configuration
  2. Check if another process is using port 1883
  3. Restart the gateway service

Device Status Shows "Unknown"

Symptoms

  • Device tile shows gray/unknown status
  • Latest values are empty

Troubleshooting

  1. Verify Device Assignment: Ensure the device is assigned to an active gateway
  2. Check Protocol Settings: Confirm IP address, port, and credentials are correct
  3. Enable Device: Ensure the Active checkbox is enabled in device settings
  4. Check Profile Tags: Verify at least one tag is defined in the device profile
warning
Passive Mode

Devices with Active unchecked will not poll for data. This is by design for batch import scenarios.

See Also

← Previous
Troubleshooting Overview
Next →
Data Flow Problems