Skip to main content
Conversational AI Engine: Create advanced voice apps by combining Agora’s real-time audio with powerful conversational AI.

Troubleshooting

This page addresses frequently encountered issues when working with TEN Agent.

Development environment problems​

Script not found error​

You see the following error:


_1
/app/agent/bin/start: not found

This error typically occurs due to incorrect line endings on Windows systems. Unix-based scripts require LF (Line Feed) endings, but Windows often uses CRLF (Carriage Return + Line Feed).

To resolve this issue:

  1. Configure Git to preserve line endings:


    _1
    git config --global core.autocrlf false

  2. After changing this setting, either:

    • Re-clone the repository, or
    • Download the ZIP file directly from GitHub

Environment variables not updating​

Changes to your .env file aren't reflected in your environment.

  1. Stop any running containers or services

  2. Edit your .env file with the new values

  3. Apply the changes:


    _3
    # For Linux/macOS
    _3
    source .env
    _3
    powershell


    _6
    # For Windows PowerShell
    _6
    Get-Content .env | ForEach-Object {
    _6
    if ($_ -match "(.+)=(.+)") {
    _6
    [Environment]::SetEnvironmentVariable($matches[1], $matches[2])
    _6
    }
    _6
    }

  4. Restart the containers or services

Network connectivity issues​

Verify both HTTPS and SSH connectivity to ensure proper operation:

  • Test HTTPS connection


    _1
    ping www.google.com

    Expected output:


    _3
    PING google.com (198.18.1.94): 56 data bytes
    _3
    64 bytes from 198.18.1.94: icmp_seq=0 ttl=64 time=0.099 ms
    _3
    64 bytes from 198.18.1.94: icmp_seq=1 ttl=64 time=0.121 ms

  • Test HTTP/API connectivity


    _1
    curl www.google.com

    Expected output (abbreviated):


    _4
    <html>
    _4
    <head><title>301 Moved Permanently</title></head>
    _4
    ...
    _4
    </html>

If these tests fail:

  • Check your network firewall settings
  • Verify proxy configurations
  • Ensure DNS resolution is working correctly

Container-specific problems​

Cannot connect to Docker container​

If you cannot access services in the container:

  1. Check container status:


    _1
    docker ps

  2. Verify port mappings:


    _1
    docker port ten_agent_dev

  3. Inspect container logs:


    _1
    docker logs ten_agent_dev

Module configuration issues​

If your modules do not work correctly:

  1. Verify API keys in your .env file

  2. Check module configuration in the playground

  3. Review logs for authentication errors

  4. Test API connectivity from within the container:


    _1
    docker exec -it ten_agent_dev curl -I https://api.openai.com

Platform-specific issues​

Windows line endings​

Windows users may encounter additional line-ending issues beyond the script error mentioned above. For a comprehensive fix:

  1. Set Git configuration:


    _1
    git config --global core.autocrlf false

  2. Fix existing files (if needed):


    _6
    # Install dos2unix if not available
    _6
    sudo apt-get install dos2unix # Linux
    _6
    brew install dos2unix # macOS
    _6
    _6
    # Convert files
    _6
    find . -type f -name "*.sh" -exec dos2unix {} \;

  3. Consider using WSL2 for a more Linux-compatible environment