Troubleshooting

Solutions for common issues with the Amplify Agent.

Agent Not Reporting

Check Agent Status

sudo systemctl status amplify-agent

Check Logs

sudo tail -100 /var/log/amplify-agent/agent.log

Common Issues

Problem	Solution
Invalid API key	Verify the key in `/etc/amplify-agent/agent.conf`
Network blocked	Ensure outbound HTTPS to `amplify.getpagespeed.com` is allowed
NGINX not detected	Ensure NGINX is running: `nginx -t`
Permission denied	Check file permissions on config and log directories

Missing Metrics

stub_status Not Working

Test the endpoint:

curl http://127.0.0.1/nginx_status

Expected output:

Active connections: 1
server accepts handled requests
 1234 1234 5678
Reading: 0 Writing: 1 Waiting: 0

Host ID Conflict

If your dashboard shows a "host ID conflict" warning, the agent registered a host identity that is already claimed by another account, so its data is not being monitored.

The agent derives its host ID from the machine's hostname and primary MAC address, not from a random value. Two machines that share both — most commonly a cloned server image (golden AMI), a recycled cloud instance whose MAC was reassigned, or a container built with a fixed MAC — produce the same ID and collide.

How to fix it

Give the affected server a unique identity, then restart the agent:

Set a unique hostname: sudo hostnamectl set-hostname my-unique-host
If the machine was cloned from an image, confirm it has its own network interface / MAC address rather than an inherited one
Restart the agent: sudo systemctl restart amplify-agent

If the machine that originally claimed the ID is gone, its host record is released automatically after 7 days of inactivity, at which point your agent claims the ID on its next check-in. Contact support if you need it released sooner.

Getting Help

If you're still having issues:

Check our FAQ for common questions
Review the agent logs for specific error messages
Contact support with your logs attached