# Troubleshooting
<a name="ct-troubleshooting"></a>

Connection refused or server not running  
The continuous modernization CLI requires a running server. Start it with `atx ct server &` and verify with `atx ct status --health`.

Discovery scan returns zero repositories  
For local sources, verify that `--path` points to a parent directory that contains repositories as subdirectories (for example, `/home/user/repos`), not to a repository directly (for example, `/home/user/repos/my-app`). The scanner looks for child directories that contain a `.git` folder.

SETUP\_REQUIRED error  
The source exists in your account but credentials are not configured on this machine. Run `atx ct source add --name {{name}}` to configure credentials locally.

AUTH\_REQUIRED error  
No valid token found for the source. Verify your token is correct and has the required scopes. For GitHub, ensure the token has `repo` scope. For GitLab, ensure `api` scope.

INVALID\_INPUT error  
Verify you are using the correct analysis type name. Valid values are: `tech-debt-quick`, `tech-debt-comprehensive`, `security`, `agentic-readiness`, `modernization-readiness`, `custom`.

Permission errors during remediation  
Remediation creates branches and pull/merge requests, which requires write access to the repository. Update your token with write permissions. For GitHub, ensure full `repo` scope. For GitLab, ensure `api` scope. For Bitbucket, ensure `write:repository:bitbucket` and `write:pullrequest:bitbucket` scopes.

Security agent setup fails  
Verify your IAM user or role has the required AWS CloudFormation, IAM, and Amazon S3 permissions listed in the Security agent setup section of [How AWS Transform continuous modernization works](continuous-modernization.md#ct-how-it-works). Check the status with `atx ct setup security-agent --status`.

Continuous modernization not visible in the web application  
If continuous modernization does not appear after you sign in to the AWS Transform web application, sign in with the IAM credentials of the AWS account where AWS Transform is enabled instead of AWS IAM Identity Center. For steps, see [AWS Transform web application (Optional)](ct-working-with.md#ct-web-application).