Server Shows Offline After a Network Change

When your server shows as offline in Server Scout after a network change, it typically means the agent has lost connectivity to the dashboard. Network configuration changes such as IP address modifications, hostname updates, firewall rule changes, DNS alterations, or network interface adjustments can disrupt the agent's connection to app.serverscout.ie.

The good news is that Server Scout's agent is designed to handle temporary outages gracefully. During connectivity issues, the agent spools monitoring data locally, so once the connection is restored, historical data will be replayed automatically and any gaps in your monitoring timeline will be filled.

Initial Diagnostics

Start by checking whether the agent service itself is running properly:

systemctl status scout-agent

If the service shows as inactive or failed, this indicates a service-level issue rather than just a connectivity problem.

Examining Agent Logs

The agent logs provide valuable insight into what's preventing connectivity:

journalctl -u scout-agent -f

Look for specific error messages such as:

• Connection timeouts or refused connections
• HTTP status codes (particularly 4xx or 5xx errors)
• DNS resolution failures
• SSL/TLS certificate errors

These log entries will help pinpoint whether the issue is network connectivity, DNS resolution, or configuration-related.

Testing Basic Connectivity

Verify that your server can reach the Server Scout dashboard:

curl -I https://app.serverscout.ie

A successful response should return HTTP status 200. If this command fails or times out, you have a fundamental connectivity issue that needs addressing at the network level.

DNS Resolution Check

Ensure your server can properly resolve the dashboard hostname:

nslookup app.serverscout.ie

Or using dig:

dig app.serverscout.ie

If DNS resolution fails, you'll need to check your server's DNS configuration in /etc/resolv.conf or verify that your network's DNS servers are accessible.

Firewall Configuration

Network changes often involve firewall modifications. Verify that outbound HTTPS traffic is permitted:

For iptables-based systems:

iptables -L -n

For firewalld systems:

firewall-cmd --list-all

The agent requires outbound access to TCP port 443 (HTTPS) to communicate with app.serverscout.ie. Ensure no rules are blocking this traffic.

Agent Configuration Verification

Check that the agent's configuration remains intact after your network changes:

cat /opt/scout-agent/agent.env

Verify that:

• The SCOUT_URL points to the correct dashboard URL
• The SCOUTAPIKEY contains your server's API key
• No configuration values were inadvertently modified during your network changes

Service Restart and Refresh

Once you've addressed any connectivity or configuration issues, restart the agent service:

systemctl restart scout-agent

After restarting, force the agent to immediately attempt communication with the dashboard:

/opt/scout-agent/scout-agent.sh --refresh

This command triggers an immediate data collection and transmission cycle, which should quickly restore your server's online status in the dashboard.

Data Recovery

One of Server Scout's key features is its resilience during connectivity issues. The agent maintains a local spool of monitoring data when it cannot reach the dashboard. Once connectivity is restored, this spooled data is automatically transmitted, ensuring your monitoring history remains complete without manual intervention.

When to Contact Support

If you've completed these diagnostic steps and your server remains offline, our AI support bot at app.serverscout.ie can provide additional troubleshooting guidance within approximately one minute. The support system can analyse your specific configuration and network setup to suggest targeted solutions.

For complex network issues requiring human expertise, tickets can be escalated to our technical team, who will review your case within 24 hours during business days.