Skip to content

Troubleshooting

The agent is not in your PATH. Either:

  1. Use the full path:

    Terminal window
    ~/.local/bin/epoch-agent --help
  2. Add to PATH:

    Terminal window
    # For bash
    echo 'export PATH="$PATH:$HOME/.local/bin"' >> ~/.bashrc
    source ~/.bashrc
    # For zsh
    echo 'export PATH="$PATH:$HOME/.local/bin"' >> ~/.zshrc
    source ~/.zshrc

macOS: “cannot be opened because it is from an unidentified developer”

Section titled “macOS: “cannot be opened because it is from an unidentified developer””

Remove the quarantine attribute:

Terminal window
xattr -d com.apple.quarantine /usr/local/bin/epoch-agent

Or allow it in System Settings > Privacy & Security.

The download may be corrupted. Try:

  1. Re-download the binary
  2. Use a different network
  3. Download directly from the releases page
  • Verify the code is copied correctly (no extra spaces)
  • Check if the code has expired (codes expire after 24 hours)
  • Generate a new code from the dashboard

Each activation code can only be used once. Generate a new code from your dashboard.

”Connection refused” during activation

Section titled “”Connection refused” during activation”

Check network connectivity:

Terminal window
# Test API connectivity
curl -v https://api.epochproxy.cloud/health
# Check DNS resolution
nslookup api.epochproxy.cloud
  1. Check the agent is running:

    Terminal window
    # If using systemd
    sudo systemctl status epoch-agent
    # If running manually, check process
    ps aux | grep epoch-agent
  2. Check network connectivity:

    Terminal window
    curl -v https://api.epochproxy.cloud/health
  3. Check firewall rules:

    • The agent needs outbound HTTPS (443) access
    • The agent uses WebSocket connections to the relay server

Usually indicates network issues:

  • Check your firewall/proxy settings
  • Verify stable internet connection
  • The agent will automatically reconnect

Enable debug logging to see what’s happening:

Terminal window
RUST_LOG=epoch_agent=debug epoch-agent

The agent hasn’t been activated yet. Run with an activation code:

Terminal window
epoch-agent --activation-code YOUR_CODE

The state file may be corrupted. Re-activate:

Terminal window
epoch-agent --force-activate --activation-code YOUR_CODE

Find where the state file is stored:

  • Linux/macOS: ~/.config/epoch-agent/state.json
  • Custom: Check --state-file argument or EPOCH_STATE_FILE env var

Check logs:

Terminal window
sudo journalctl -u epoch-agent -n 50 --no-pager

Common causes:

  • State file permissions
  • Binary not found at specified path
  • Network not ready at boot

Check status:

Terminal window
launchctl list | grep epochproxy

View logs:

Terminal window
cat ~/Library/Logs/epoch-agent.log

Enable verbose logging to diagnose issues:

Terminal window
# Debug level
RUST_LOG=epoch_agent=debug epoch-agent
# Trace level (very verbose)
RUST_LOG=epoch_agent=trace epoch-agent
# Log to file
RUST_LOG=epoch_agent=debug epoch-agent 2>&1 | tee agent.log

If you’re still having issues:

  1. Check the documentation
  2. Enable debug logging and review the output
  3. Contact support with:
    • Agent version (epoch-agent --version)
    • Operating system and version
    • Debug log output
    • Steps to reproduce the issue