# Troubleshooting

SonarQube MCP Server's logs will be written to the `<STORAGE_PATH>/logs/mcp.log` file, as defined by your [#base-variables](https://docs.sonarsource.com/sonarqube-mcp-server/build-and-configure/environment-variables#base-variables "mention").

If your MCP server is running in a container and you're using its default storage path, check the `/app/storage/logs/mcp.log` file within the running container.

When `SONARQUBE_DEBUG_ENABLED` is set to `true`, debug logging is enables. Debug logs are written to both the log file and STDERR. This parameter is useful for troubleshooting connectivity or configuration issues. Default: `false`.

## Common Issues

### "Feature is not working" or "Missing tools/functionality"

You may be running an outdated Docker image. Docker caches images locally, so you won't automatically receive updates.

**Solution:** Update to the latest version:

```bash
docker pull mcp/sonarqube:latest
```

After pulling the latest image, restart your MCP client to use the updated version.

Optionally, add the `--pull=always` flag to your docker run command to always check for and pull the latest version:

```bash
docker run --init --pull=always -i --rm -e SONARQUBE_TOKEN -e SONARQUBE_ORG mcp/sonarqube
```

*More troubleshooting content will be coming soon.*