Solutions for common issues and frequently asked questions
This error occurs when the OAuth authentication system hasn't been configured to recognize your domain. We're working with our hosting provider to register the necessary redirect URIs for cloudzentrix.io.
Click "Get Started" or "Sign In" on the home page. You'll be redirected to the Manus OAuth portal to authenticate.
Once logged in, go to the Dashboard and click "Add AWS Account". You can connect using:
After connecting your AWS account, the toolkit will automatically discover your VPCs, subnets, security groups, and network resources.
Create a new assessment to analyze your network infrastructure. The toolkit will run security checks, compliance validation, and generate recommendations.
View detailed findings, recommendations, and compliance scores. Export reports as PDF or JSON for sharing with your team.
Yes. We recommend using cross-account IAM roles with read-only permissions. Your credentials are encrypted and never stored in plain text. We only read your network configuration - we never make changes to your infrastructure.
Yes. You can add multiple AWS accounts and run assessments across all of them. The Multi-Account Aggregator in Advanced Tools provides a unified view of your entire network infrastructure.
Only read-only permissions are required. The toolkit needs access to:
Assessments are run on-demand when you create them. You can create new assessments at any time to get the latest snapshot of your network infrastructure.
Yes. All assessments can be exported as PDF or JSON. PDF reports include formatted findings, recommendations, and compliance scores. JSON exports provide structured data for integration with other tools.
Windows Defender Firewall prompts for any new executable that tries to open a network connection. The CloudZentrix Agent needs outbound access on port 443 (HTTPS / WebSocket) to reach the dashboard and send metrics. If you see the popup, click Allow access.
Starting from installer v2.4, the setup script automatically adds the required firewall rules — you should not see the popup on fresh installs. The agent also adds the rules silently on startup if they are missing.
$exe = "$env:ProgramFiles\CloudZentrixAgent\agent.exe" Remove-NetFirewallRule -DisplayName "CloudZentrix Agent*" -ErrorAction SilentlyContinue | Out-Null New-NetFirewallRule -DisplayName "CloudZentrix Agent (Outbound)" -Direction Outbound -Program $exe -Action Allow -Protocol TCP -RemotePort 443 -ErrorAction SilentlyContinue | Out-Null New-NetFirewallRule -DisplayName "CloudZentrix Agent (Outbound-80)" -Direction Outbound -Program $exe -Action Allow -Protocol TCP -RemotePort 80 -ErrorAction SilentlyContinue | Out-Null Write-Host "Done — firewall rules applied." -ForegroundColor Green
This removes any existing (possibly blocking) rules and adds clean outbound allow rules for agent.exe on ports 443 and 80. Requires Administrator privileges.
Get-NetFirewallRule -DisplayName "CloudZentrix Agent*" | Select-Object DisplayName, Direction, Action, Enabled
You should see two rules with Action = Allow and Enabled = True. If they are missing or show Action = Block, run the Fix Firewall one-liner above.
If your organisation manages firewall policy via Intune, Group Policy, or a third-party endpoint security product, the Windows Firewall rules above may be overridden. Ask your IT/security team to allow:
C:\Program Files\CloudZentrixAgent\agent.exe*.cloudzentrix.com, *.manus.computer (WebSocket relay)The agent never opens inbound ports — all communication is outbound from the monitored machine to the CloudZentrix cloud.
If you're experiencing issues not covered here, our support team is ready to help.