Troubleshooting Guide

curl http://localhost:8080/api/check-credentials

# Is something already on the port?
lsof -i :8080            # macOS/Linux
netstat -tulpn | grep :8080

# Is kollect running?
ps aux | grep kollect

AWS shows "Not Connected".

1. Test CLI access: aws sts get-caller-identity
2. Check credentials exist: ls ~/.aws/
3. Try directly: ./kollect --inventory aws

ec2:Describe*
s3:ListAllMyBuckets
s3:GetBucket*
rds:Describe*
dynamodb:ListTables
dynamodb:DescribeTable

Azure shows "Not Connected".

1. Check the session: az account show
2. Log in if needed: az login
3. Try directly: ./kollect --inventory azure

GCP shows "Not Connected".

1. Check auth: gcloud auth list / gcloud config get-value project
2. Set application-default credentials: gcloud auth application-default login
3. Try directly: ./kollect --inventory gcp

Kubernetes shows "Not Connected".

1. Test access: kubectl cluster-info / kubectl get nodes
2. Check contexts: kubectl config get-contexts
3. Point at a specific config/context:

   ./kollect --inventory kubernetes --kubeconfig ~/.kube/config --kube-context prod

OpenShift uses the same kubeconfig — collect it with ./kollect --inventory openshift.

Docker shows "Not Connected" or "permission denied".

1. Test the daemon: docker info / docker ps
2. On Linux, add your user to the docker group: sudo usermod -aG docker $USER (then log out/in)
3. Point at a specific socket/host:

   ./kollect --inventory docker --docker-host unix:///var/run/docker.sock

vSphere shows "Not Connected".

1. Check connectivity: ping vcenter.example.com
2. Connect with flags (add --vsphere-insecure for self-signed certs):

   ./kollect --inventory vsphere \
     --vsphere-server vcenter.example.com \
     --vsphere-username readonly@vsphere.local \
     --vsphere-password '******' \
     --vsphere-insecure

3. Or use VSPHERE_SERVER / VSPHERE_USERNAME / VSPHERE_PASSWORD / VSPHERE_INSECURE.

Hyper-V connection fails or returns an empty body / 500.

1. Kollect connects over WinRM. Domain hosts that enforce message encryption need HTTPS: add --hyperv-https.
2. For domain accounts, try Kerberos: --hyperv-auth kerberos (with --hyperv-realm / --hyperv-kdc if discovery fails).
3. To include a failover cluster's nodes, add --hyperv-cluster.
4. Confirm WinRM is enabled on the host (Enable-PSRemoting) and reachable on 5985/5986.

Proxmox or Nutanix shows a certificate error.

1. Both commonly use self-signed certificates — add --proxmox-insecure or --nutanix-insecure.
2. Proxmox accepts either an API token (--proxmox-token user@realm!id=secret) or username/password.
3. Nutanix Prism Element listens on port 9440 by default.

Terraform shows "Not Connected".

1. Local state: ./kollect --inventory terraform --terraform-state ./terraform.tfstate
2. Remote S3: ./kollect --inventory terraform --terraform-s3 mybucket/prod.tfstate --terraform-s3-region us-east-1

Vault shows "Not Connected".

1. Test health: curl -k https://vault.example.com:8200/v1/sys/health
2. Provide address and token via env or flags:

   export VAULT_ADDR="https://vault.example.com:8200"
   export VAULT_TOKEN="s.abc123..."
   ./kollect --inventory vault

export HTTP_PROXY=http://proxy.company.com:8080
export HTTPS_PROXY=http://proxy.company.com:8080
export NO_PROXY=localhost,127.0.0.1

curl -I https://ec2.amazonaws.com
curl -I https://management.azure.com
curl -I https://compute.googleapis.com

uname -a
./kollect --help          # confirm the flags available in your build
curl http://localhost:8080/api/check-credentials