/command/. | Cannot connect to the P0 API endpoint (DNS, proxy, firewall). | Verify your internet connection and DNS lookup.
Check appUrl in \~/.p0/config.json
Whitelist the endpoint in your proxy/firewall.
|
| fetch failed | Underlying fetch call timed out or TLS handshake failed. | Test reachability with curl https\://\/o/\/command/
Ensure your system clock is accurate (TLS requires correct time).
|
***
#### **3. Flag & Usage Errors**
| **Error Message** | **Cause** | **Resolution** |
| -------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------ |
| Unknown argument: --foo | Typo or unsupported flag. | Check flags with p0 ls --help or p0 ls \ --help. |
| Invalid number for '--size' | Non-integer or out-of-range value provided. | Use a positive integer: e.g. --size 20. |
| No output, even though resources exist | You omitted the provider or subcommand. | Ensure you specify a valid provider and subcommand (e.g., p0 ls aws resource). |
| No \ | The backend returned zero matches for your query. | Remove or change your search term/filter; try running without arguments. |
***
#### **4. Subcommand & Provider Validation**
| **Symptom** | **Cause** | **Resolution** |
| --------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| Unknown command: ssh | Misspelling or integration not recognized. | Verify integration names with p0 ls --help (must be ssh, not sShh, etc.). |
| Empty list from p0 ls ssh session destination | No session destinations match your filter or you lack permissions. | Try a broader or different search term.
Confirm your account has at least one session destination assigned.
|
| Backend error JSON (for example, permission denied) | Your P0 role or tenant configuration does not allow listing. | Ensure your P0 admin has granted your role the "list" permission for that provider integration. |
***
#### **5. Pagination & Truncation Questions**
* **"Showing the first N…" but you know there are more**
* CLI fetched 2×size to detect truncation; your --size controls only display.
* **Resolution**: Increase --size to show more items, or add a filter term.
* **Suggestion "use \ to narrow results"**
* This indicates isTruncated=true and no search term was provided.
* **Resolution**: Add a search argument after your subcommand (e.g., p0 ls aws resource logs).
***
#### **6. JSON Mode Issues**
* **Invalid JSON output or parse errors**
* Occurs if the backend returns malformed JSON.
* **Resolution**:
1. Run without --json to see the human output.
2. Contact P0 support if the payload is not valid JSON.
***
1. **Enable debug `--debug`**
2. Prints HTTP request/response details to stderr.
3. **Check local config**
```plaintext
cat ~/.p0/config.json
```
2. Verify appUrl and any proxy settings.
3. **Test API directly**
```plaintext
curl -X POST https:///o//command/ \
-H "Authorization: Bearer $(token)" \
-d '{"argv":["ls","aws","resource",""],"scriptName":"p0"}'
```
4. Examine raw JSON to ensure the backend is returning items.
5. **Validate provider-side state**
If you expect resources to exist, confirm in the native console or CLI (e.g., aws s3 ls, kubectl get pods, etc.).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.p0.dev/p0-cli/troubleshooting/p0-ls.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.