Troubleshooting Guide

Solutions for common CloudMapper issues and problems

Get Help on GitHub

For all technical support, troubleshooting, and questions, please use our GitHub repository where the community and maintainers can help you.

Ask Questions Report Issues

Quick Solutions

Installation Problems

CloudFormation deployment issues, AMI not found, instance fails to start.

Get Installation Help

Access Issues

Cannot access web interface, login failures, SSL certificate errors.

Get Access Help

Scanning Problems

Scan failures, missing resources, slow performance, permissions issues.

Get Scanning Help

Common Diagnostic Commands

Check System Status

# Service status
sudo systemctl status cloudmapper
sudo systemctl status nginx

# Resource usage
free -h
df -h

Check AWS Connectivity

# AWS credentials
aws sts get-caller-identity

# Test permissions
aws ec2 describe-regions

Check SSH Configuration

# Check if SSH is enabled
sudo systemctl status sshd

# Check SSH configuration
sudo cat /etc/ssh/sshd_config | grep -E "^(PermitRootLogin|PasswordAuthentication|PubkeyAuthentication|AllowUsers)"

SSH Access Troubleshooting (v1.1.0+ with FIPS)

SSH is disabled by default. CloudMapper uses SSM Session Manager for secure access (recommended). SSH can be optionally enabled for AWS Marketplace scanning.

FIPS Mode Requirement

CloudMapper runs in FIPS 140-2 mode. Standard SSH connections will fail with "Connection closed by remote host" during key exchange.

You MUST use FIPS-compliant algorithms when connecting via SSH.

Enable SSH Access:

Provide a valid KeyName parameter (enables SSH automatically)
No EnableSSH parameter needed (removed in v1.1.0)
SSH hardened: public key only, ec2-user only, connection limits

Connect with FIPS Algorithms:

ssh -o "KexAlgorithms=ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521" \
    -o "Ciphers=aes128-ctr,aes192-ctr,aes256-ctr" \
    -i ~/.ssh/your-key.pem ec2-user@instance-ip

Common SSH Issues:

Connection closed by remote host: Using non-FIPS algorithms (see solution below)
Permission denied (publickey): Wrong key or user (must use ec2-user)
Timeout: AllowedCIDR parameter doesn't include your IP (default: 10.0.0.0/8)
Too many authentication failures: MaxStartups limit (3 concurrent connections max)

Permanent SSH Config Fix:

Add to ~/.ssh/config:

Host cloudmapper *.cloudmapper.*
  User ec2-user
  KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384
  Ciphers aes128-ctr,aes256-ctr
  MACs hmac-sha2-256,hmac-sha2-512

View Complete SSH Access Guide

GitHub Support Resources

GitHub Discussions

Get help from the CloudMapper community:

Ask questions and get answers
Share troubleshooting experiences
Learn from other users' solutions
Get help with configuration

Join Discussions

GitHub Issues

Report bugs and technical issues:

Report installation problems
Submit bug reports with logs
Request new features
Track issue resolution

Create Issue

Best Practices for Getting Help

Search first: Check existing discussions and issues before creating new ones
Provide details: Include error messages, logs, and your configuration
Use templates: Follow our issue templates for faster resolution
Be specific: Describe what you expected vs. what actually happened

View Repository

Emergency Recovery Procedures

Service Recovery:

# Stop services
sudo systemctl stop cloudmapper nginx

# Clear cache and temp files
sudo rm -rf /opt/cloudmapper/cache/*
sudo rm -rf /tmp/cloudmapper-*

# Restart services
sudo systemctl start nginx cloudmapper
sudo systemctl status cloudmapper

Data Backup:

# Create EBS snapshot
aws ec2 create-snapshot \
  --volume-id vol-1234567890abcdef0 \
  --description "CloudMapper backup"

# Manual data backup
sudo tar -czf /tmp/cloudmapper-backup.tar.gz \
  /opt/cloudmapper/config \
  /opt/cloudmapper/data

Critical Issues: For severe problems, consider launching a new CloudMapper instance and migrating your configuration. Ask for help on GitHub before attempting recovery procedures.

Documentation

AWS Marketplace

Quick Help