Troubleshooting Guide¶
Common issues and how to resolve them.
Range Issues¶
Range Stuck in "Provisioning"¶
Symptoms: Status shows "Provisioning" for more than 10 minutes.
Solutions:
- Wait a bit longer - some scenarios take 10-15 minutes
- Cancel the range and relaunch
- If repeated failures, check your agent file is valid
Range Shows "Failed"¶
Symptoms: Status shows "Failed" with an error message.
Solutions:
- Read the error message - it usually indicates the cause
-
Check your agent file:
-
Is it the right format for the OS you selected?
- Is the file corrupted? Try re-downloading from your console
- Try a different scenario (Basic Range is most reliable)
- Destroy and relaunch
Can't Launch Range - "Already Have Active Range"¶
Symptoms: Launch button disabled or error about existing range.
Solution: Destroy your current range first. Go to Ranges, click Destroy on the active range.
Terminal Issues¶
Terminal Won't Connect¶
Symptoms: Terminal shows "Connecting..." indefinitely or "Not connected."
Solutions:
- Refresh the page
- Wait a minute - instance may still be starting
- Check if range is in "Ready" status
- Try a different browser
Terminal Disconnects Frequently¶
Symptoms: Connection drops, have to reconnect.
Solutions:
- Check your network connection
- Avoid letting the browser tab go idle for long periods
- Refresh and reconnect
RDP Button Does Nothing¶
Symptoms: Clicking RDP doesn't open a new window.
Solutions:
- Check browser popup blocker - allow popups from BigRAE
- Try right-click > "Open in new tab"
- Wait for instance to fully boot (RDP service may not be ready)
Agent Issues¶
Upload Fails¶
Symptoms: Upload errors or stuck at 0%.
Solutions:
- Check file size - max 2 GB per file
- Check total storage - max 5 GB across all agents
- Verify file format is supported
- Try a different browser
- Check network connection
Agent Shows Wrong OS¶
Symptoms: Agent listed as wrong platform.
Cause: OS is detected from file format, not contents.
Solution: If detection is wrong, delete and re-upload with correct format. Ensure you're using:
.msior.zipfor Windows.tar.gzfor Linux shell installer.debfor Debian/Ubuntu.rpmfor RHEL/CentOS
No Alerts in Console After Attack¶
Symptoms: Running attacks but no alerts appear.
Solutions:
-
Verify agent is installed and connected:
-
Check your XDR/XSIAM console for agent status
- Agent should show as "Connected" or similar
-
Run a more obvious attack:
-
Execute known malware samples
- Run detection test tools
- Trigger behavioral detections
-
Check console filters:
-
Ensure you're looking at the right time range
- Check severity filters aren't hiding alerts
- Wait a few minutes - some alerts take time to process
NGFW Issues¶
NGFW Stuck Provisioning¶
Symptoms: Provisioning progress stuck for 30+ minutes.
Solutions:
- NGFW provisioning genuinely takes 15-30 minutes - be patient
- If stuck beyond 45 minutes, try deprovisioning and starting over
- Verify your deployment profile authcode is valid
- Check SCM credential has correct PIN
Can't Associate Device in SCM¶
Symptoms: SCM rejects the serial number or association fails.
Solutions:
- Double-check serial number (copy-paste to avoid typos)
- Verify SCM folder exists and accepts new devices
- Check PIN hasn't expired
- Ensure you have permissions in SCM
NGFW-Enabled Range Won't Launch¶
Symptoms: Launching Basic Range with NGFW or Cortex BYOT fails.
Solutions:
- Verify NGFW status is "Ready" (not "Provisioning" or "Failed")
- Complete SCM association and XDR/XSIAM connection first
- Check NGFW wasn't deprovisioned
No Network Alerts in XDR/XSIAM¶
Symptoms: Have endpoint alerts but no network/NGFW alerts.
Solutions:
- Verify NGFW is connected in XDR/XSIAM settings
- Check log forwarding is configured in SCM
-
Generate network traffic that produces logs:
-
HTTP requests (not just ICMP/ping)
- Known bad URLs or IPs
- Suspicious traffic patterns
Account Issues¶
Can't Access Certain Features¶
Symptoms: Buttons disabled, features unavailable.
Solutions:
- Ensure you're logged in
- Check if feature requires setup first (for example NGFW scenarios require NGFW)
- Contact support if you believe this is an error
Getting More Help¶
If none of these solutions work:
- Note the exact error message
- Note what you were trying to do
- Contact support (see Support)