1. Automox
  2. Using Automox
  3. Device Connection & Management

Troubleshooting Connection Issues on Linux

Avatar
Jordan
Updated:

Objective

To provide a step-by-step guide for diagnosing and resolving network connectivity issues on Linux endpoints, ensuring the Automox Agent can communicate with Automox servers.

Overview

Network disruption, restrictive local firewalls, or stale service configurations can prevent Linux endpoints from connecting to local networks or reaching Automox cloud endpoints (api.automox.com). Following a systematic troubleshooting workflow helps restore connectivity and agent check-ins.

Troubleshooting Workflow

1.Check Network Interface Settings:

Verify that physical or wireless network interfaces are enabled and properly configured. You can inspect interface states using your desktop environment's network panel or via terminal:

ip addr show

Ensure your interface (eth0, wlan0, etc.) has an active IP assignment.

2.Test Network & Automox Endpoint Connectivity:

Verify that your system can reach external networks and the Automox cloud infrastructure by sending ICMP ping requests:

ping -c 4 api.automox.com
  • Successful Response: The system has basic network connectivity and can resolve Automox DNS entries.
  • Request Timeout / Host Unreachable: The system cannot reach Automox servers. Proceed to check network services and firewall rules.

3.Restart Network Management Services:

If network interfaces are unresponsive or stuck, restart local network management daemons:

  • For Systemd NetworkManager (Ubuntu/Debian/RHEL/CentOS):
sudo systemctl restart NetworkManager
  • For Systemd Networkd:
sudo systemctl restart systemd-networkd

After restarting, re-test connectivity by pinging api.automox.com.

4.Inspect Local Firewall Settings (UFW / firewalld):

Check if local firewall rules or blocked ports are preventing outbound Automox traffic:

  • Uncomplicated Firewall (UFW - Debian/Ubuntu):
sudo ufw status

If outbound traffic is restricted, ensure required outbound ports (such as HTTPS 443) are allowed:

sudo ufw allow out 443/tcp
  • Firewalld (RHEL/CentOS/Fedora):
sudo firewall-cmd --state

(For a complete list of required IP ranges and URLs, see [Agent Firewall Allowlisting Rules](Agent Firewall Allowlisting Rules)).

5.Update Network Drivers and System Packages:

Outdated network interface drivers or kernel modules can cause intermittent connectivity drops. Update system software and drivers using your distribution's package manager:

  • Debian / Ubuntu:
sudo apt-get update && sudo apt-get upgrade -y
  • RHEL / CentOS / Fedora:
sudo dnf upgrade -y

Reboot the endpoint after completing updates to load updated network drivers.

Next Steps

If network connectivity is established but the Automox Agent is still failing to check in, restart the Automox Agent service:

sudo systemctl restart amagent

Articles in this section

See more
Was this article helpful?
0 out of 0 found this helpful