LogoLogo
Back to binalyze.com
  • Welcome | Binalyze Knowledge Base
  • AIR
    • AIR
    • Introduction
      • What is AIR?
      • Terminology
      • Architecture
        • AIR Responder Architecture; overview and performance analysis
        • AIR Task Flow and Management
      • Network Communication
      • Cloud Forensics with Binalyze AIR
    • AIR Setup
      • Console Hardware Requirements
      • Console Pre-Installation
      • Console Installation
      • Microsoft Azure Cloud Platform Integration
      • AIR Relay Server
        • What is AIR Relay Server?
        • Requirements for installation
        • How to install a Relay Server on different Linux platforms
        • How to change IP address of Relay Server
        • How to install a Responder with Relay Server support
        • Proxy configurations
          • Adding proxy to Relay Server
          • Adding proxy to Responder
        • Service Management for Relay Server
        • Whitelisting for Relay Server
        • Retrieving metrics from Relay Server
        • Updating and Uninstalling Relay Server
        • Troubleshooting
      • AIR Responder - Supported Operating Systems
        • AIR Responder - MS Windows supported systems
        • AIR Responder - Apple macOS supported systems
        • AIR Responder - Linux (DEB/RPM) supported systems
        • AIR - ESXi Standalone Collector
        • AIR Responder - Chrome supported systems
          • AIR For Chrome
      • AIR Responder Hardware Requirements
      • AIR Responder Deployment
        • Golden Image
        • Responder & Active Directory OUs
        • AIR Responder Exception Rules
          • Binalyze AIR Watchdog Folder
        • FDA via Jamf and Apple’s PPPC utility
        • AIR Responder in Windows 'Safe Mode'
      • Uninstalling AIR Responders
      • Security
        • AIR Console Access Control
        • AIR SSL Enforcement
          • SSL Certificate Management in Binalyze AIR
        • Two-factor authentication (2FA)
      • Post-Deployment Configuration Guide
        • Using AIR CLI on Binalyze AIR Console
    • AIR's User Settings
      • General
      • Assets
      • Security
      • Features
      • Evidence Repositories
      • Policies
      • User Management
        • User Groups
        • User Roles
      • Backup
      • Investigation Hub Disk Usage
      • Danger Zone
    • Updating AIR
      • Single-Tier Systems
      • 2-Tier Systems
      • AIR Console Updating - SaaS
    • Backup
      • Restore AIR Backup using the CLI
    • Features
      • Acquisition
        • Task Creation
          • Regex in AIR/DRONE:
          • Asset Management with Persistent Saved Filters
          • Task Cancellation and Deletion
        • Acquisition Profiles
        • Supported Evidence
          • Windows Collections
          • macOS Collections
          • Linux Collections
          • IBM AIX Collections
        • Scheduling Tasks
        • Disk and Volume Imaging
          • Imaging with interACT
        • Chain Of Custody in AIR
      • Auto Tagging
      • Triage
        • Triage Rule Templates
          • YARA Templates
          • Sigma Templates
          • osquery Templates
        • Schedule Triage Tasks
      • interACT
        • interACT Commands
        • PowerShell commands in interACT
      • Compare
      • Timeline
      • Integrations
        • SSO Integrations
          • Microsoft Azure SSO Integration
          • Okta SAML 2.0 SSO Integration
        • Webhooks
          • Mattermost Integration
          • Splunk Integration
          • IBM QRadar Integration
          • Wazuh Integration
          • Cortex XSOAR Integration
          • Elasticsearch Logstash Kibana Integration
          • ServiceNow Integration
          • Sumo Logic Integration
          • Crowdstrike Integration
          • Microsoft Sentinel Integration
          • Slack Integration
          • Carbon Black Cloud Integration
          • Rapid7 InsightIDR Integration
          • LogicHub SOAR (DEVO) Integration
          • Fortigate SIEM Integration
          • Dynatrace Integration
          • Stellar XDR Integration
          • SentinelOne Integration
          • Microsoft 365 Defender Integration
          • Cisco XDR Integration
      • Event Subscription
      • AIR API
        • API in AIR is likely to be more effective than Webhooks
      • DRONE
        • What is DRONE?
        • What is an Analysis Pipeline?
        • Analyzers
          • Cross Platform Analyzers
            • MITRE ATT&CK Analyzer
              • MITRE ATT&CK Analyzer changelog
            • Dynamo Analyzer
            • Browser History Analyzer
            • Generic WebShell Analyzer
          • Windows Analyzers
            • Windows Event Records and how AIR handles them
              • Windows Event Logs in AIR v4.21 and older versions
              • Event Records Summary vs. Event Records
            • Prefetch Analyzer
            • Shellbag Data Fields
          • Linux Analyzers
          • macOS Analyzers
            • Audit Event Analyzer
      • AIR Investigation Hub
        • Using the AIR Investigation Hub
        • Investigation Hub – Data Usage Statistics Dashboard
      • AIR File Explorer
        • File Explorer - FAQs
      • Tornado (Preview Version)
        • Tornado Installation Guide
          • Tornado Operating System Support
        • Updating Tornado
        • Tornado demo video
        • Getting Started with Tornado
          • Tornado Terminology
        • Tornado Collectors
          • Accessing Google Workspace
            • Service Account Creation
              • Enable Service Account Key Creation
          • Access Modes in O365
            • O365 license types
        • Tornado Troubleshooting & Feedback
        • Tornado FAQs
      • Frank.AI
      • Asset Isolation
      • Evidence Repositories
      • Policies
      • Tags
      • Off-Network Responder
        • Setting Up a Custom Case Directory
        • biunzip
          • biunzip password file
      • Binalyze AIR Responder Proxy Support
      • Proxy Configuration on Binalyze AIR Console
      • Binalyze AIR Audit Logs
    • Troubleshooting
      • Binalyze AIR Console CPU Profiling for Performance Issues
      • Understanding MSI Error Code 1618
      • How to gather Binalyze AIR logs for Troubleshooting
        • Collecting Binalyze AIR Console Log Files
        • Collecting Binalyze AIR Responder Log Files
        • Collecting Binalyze AIR Off-Network Responder Log Files
    • FAQs
      • Binalyze AIR Console Migration Procedure For Single-Tier Setup
      • Binalyze AIR Console Migration Procedure For 2-Tier Installation
      • Binalyze AIR Console Backup Procedure
      • Resolving the “Invalid Host Header. Host must be the Console Address” Error
      • How to download the collected evidence and artifacts in Binalyze AIR?
      • How to gather Binalyze AIR logs for Troubleshooting
        • Collecting Binalyze AIR Console Log Files
        • Collecting Binalyze AIR Responder Log Files
        • Collecting Binalyze AIR Off-Network Responder Log Files
      • AIR responder troubleshooting
      • Understanding Port Usage in Binalyze AIR
      • How many assets can connect to a single Console instance?
      • How do I enable SSL on AIR?
      • Can I use AIR with EDR/XDR Products?
      • Can I integrate AIR with my SOAR/SIEM?
      • What (sub)domains are used by AIR?
      • Docker & Host System IP Conflict
      • Monitoring Responder and UI API's
      • How do I update AIR Console?
      • How do I update AIR Responders on assets?
      • How to reset the password of a user via the AIR-CLI?
      • Is there a way to move an asset from one Organization or Case to another?
      • Creating exclusions/exception rules for Binalyze AIR Responder on EPP and EDR Solutions
      • Anything missing?
      • How can I install a version of AIR that isn't the latest?
  • General
    • Licenses - Open-source Software List
Powered by GitBook
On this page
  • 1. What Does the “Invalid Host Header” Error Mean?
  • 2. Why Did This Error Appear After Upgrading?
  • 3. How Do I Fix This Error?
  • 4. What Should I Use as My Console Address: IP or Domain?
  • 5. Troubleshooting Tips
  • 6. Reference Articles

Was this helpful?

Export as PDF
  1. AIR
  2. FAQs

Resolving the “Invalid Host Header. Host must be the Console Address” Error

This FAQ explains why the “Invalid Host Header” error occurs, how to resolve it, and how to add multiple console addresses for Binalyze AIR.


1. What Does the “Invalid Host Header” Error Mean?

From AIR Console version 4.33 onward, Binalyze AIR strictly enforces the configured Console Address as a security measure to prevent unauthorized access.

If you see the error:

"Invalid Host Header. Host must be the Console Address",

This means that AIR is receiving requests from an unapproved address. This behavior was introduced to mitigate Host Header injection vulnerabilities.


2. Why Did This Error Appear After Upgrading?

If you upgraded from pre-4.33 versions (e.g., 4.31.x or 4.23.x) to 4.33 or later, the new security measures require you to explicitly whitelist console addresses (IP addresses or domain names) in the AIR environment file.


3. How Do I Fix This Error?

To resolve this issue, you need to define the AIR_CONSOLE_ADDRESSES environment variable in the .env file. Follow these steps:

Step 1: Access the AIR Console Server

Log into the server (via SSH) where the Binalyze AIR Console is hosted.

Step 2: Back Up the Environment File

Run the following command to create a backup of the .env file:

cp -v /opt/binalyze-air/volumes/app/binalyze-air/config/.env \
     /opt/binalyze-air/volumes/app/binalyze-air/config/.env-BACKUP

Step 3: Add Additional Console Addresses

Use the following command to append the new console address:

echo "AIR_CONSOLE_ADDRESSES=<YOUR_ADDRESS>" >> /opt/binalyze-air/volumes/app/binalyze-air/config/.env
  • Replace <YOUR_ADDRESS> with the IP or domain name you want to allow.

    • Example:

      AIR_CONSOLE_ADDRESSES=my-air-console.example.com
  • If multiple addresses are needed, separate them with commas:

    AIR_CONSOLE_ADDRESSES=my-air-console.example.com,10.0.0.50

Step 4: Restart the Containers

After updating the .env file, restart the AIR containers:

cd /opt/binalyze-air
docker compose down && docker compose up -d

Step 5: Verify Access

Once the containers are up, log in using the newly added console addresses. If the error persists:

  • Check for typos in the .env file.

  • Ensure case-sensitivity matches browser behavior (browsers often lowercase domain names).

  • Confirm DNS/host settings are correct.


4. What Should I Use as My Console Address: IP or Domain?

You can add any valid address, such as: ✅ IP Addresses (e.g., 10.0.0.50) ✅ Fully Qualified Domain Names (FQDNs) (e.g., my-air-console.example.com)

💡 If you plan to connect using multiple addresses (e.g., internal IP + domain), add all of them to AIR_CONSOLE_ADDRESSES.

📌 Important: Browsers may automatically lowercase domain names, so ensure your entry in .env matches how users type it.


5. Troubleshooting Tips

🔍 Case Sensitivity Issues

  • Some browsers convert uppercase domain names to lowercase. Ensure your .env file reflects this behavior.

📂 Backup & Revert if Needed

  • If an update causes issues, restore your backup and restart the containers.

cp -v /opt/binalyze-air/volumes/app/binalyze-air/config/.env-BACKUP \
    /opt/binalyze-air/volumes/app/binalyze-air/config/.env
docker compose down && docker compose up -d

🌐 Network & DNS Configuration

  • Ensure DNS records and network settings reflect your environment.


6. Reference Articles

📌 AIR Console Access Control

📌 Binalyze AIR Release Notes


We hope this FAQ helps you resolve the “Invalid Host Header” error and keep your Binalyze AIR environment secure.

For further troubleshooting, please contact [email protected]

PreviousBinalyze AIR Console Backup ProcedureNextHow to download the collected evidence and artifacts in Binalyze AIR?

Last updated 2 months ago

Was this helpful?

explains the security updates enforcing approved console addresses to prevent Host Header injection.

Track news regarding new and enhanced security measures in our .

This page in the Binalyze Knowledge Base
release notes