Skip to content

added more solutions to troubleshooting section #2485

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

added more solutions to troubleshooting section #2485

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions docs/deploy_troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,3 +11,29 @@
1. You see `CERTIFICATE_VERIFY_FAILED` when the `prepdocs.py` script runs. That's typically due to incorrect SSL certificates setup on your machine. Try the suggestions in this [StackOverflow answer](https://stackoverflow.com/questions/35569042/ssl-certificate-verify-failed-with-python3/43855394#43855394).

1. After running `azd up` and visiting the website, you see a '404 Not Found' in the browser. Wait 10 minutes and try again, as it might be still starting up. Then try running `azd deploy` and wait again. If you still encounter errors with the deployed app and are deploying to App Service, consult the [guide on debugging App Service deployments](/docs/appservice.md). Please file an issue if the logs don't help you resolve the error.

# How to resolve other potential error messages:

Check failure on line 15 in docs/deploy_troubleshooting.md

View workflow job for this annotation

GitHub Actions / Check for Markdown linting errors 

Multiple top-level headings in the same document [Context: "How to resolve other potential..."]

Check failure on line 15 in docs/deploy_troubleshooting.md

View workflow job for this annotation

GitHub Actions / Check for Markdown linting errors 

Trailing punctuation in heading [Punctuation: ':']

This section covers common error messages you might encounter when deploying templates locally, along with solutions to resolve them.

- [Quota and resources available: InsufficientQuota](./deploy_troubleshooting.md#error-message-quota-and-resources-available-insufficientquota)
- [The subscription ID cannot have more than 2 container app environments](#maxnumberofglobalenviromentsinsubexceeded-the-subscription-id-cannot-have-more-than-2-container-app-environments)

## Error message: Quota and resources available: InsufficientQuota:

Check failure on line 22 in docs/deploy_troubleshooting.md

View workflow job for this annotation

GitHub Actions / Check for Markdown linting errors 

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## Error message: Quota and resources available: InsufficientQuota:"]

Check failure on line 22 in docs/deploy_troubleshooting.md

View workflow job for this annotation

GitHub Actions / Check for Markdown linting errors 

Trailing punctuation in heading [Punctuation: ':']
_This operation require 30 new capacities in quota Tokens Per Minute (thousands) - GPT-35-Turbo, which is bigger than the current available capacity 0. The current quota usage is 30 and the quota limit is 30 for quota Tokens Per Minute (thousands) - GPT-35-Turbo._

Possible solutions:

Check failure on line 25 in docs/deploy_troubleshooting.md

View workflow job for this annotation

GitHub Actions / Check for Markdown linting errors 

Trailing spaces [Expected: 0 or 2; Actual: 1]

1. Review and adjust the quota: Check if you can increase the quota for Tokens Per Minute (thousands) for your gpt-model in your Azure settings. This might involve requesting a quota increase through the Azure portal.

Check failure on line 27 in docs/deploy_troubleshooting.md

View workflow job for this annotation

GitHub Actions / Check for Markdown linting errors 

Hard tabs [Column: 3]
2. Contact Azure support: If you can't adjust the quota yourself, reach out to Azure support with the tracking ID for specific assistance with your issue.

Check failure on line 28 in docs/deploy_troubleshooting.md

View workflow job for this annotation

GitHub Actions / Check for Markdown linting errors 

Hard tabs [Column: 3]

## MaxNumberofGlobalEnviromentsInSubExceeded: The subscription ID cannot have more than 2 container app environments.

Check failure on line 30 in docs/deploy_troubleshooting.md

View workflow job for this annotation

GitHub Actions / Check for Markdown linting errors 

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## MaxNumberofGlobalEnviromentsInSubExceeded: The subscription ID cannot have more than 2 container app environments."]

Check failure on line 30 in docs/deploy_troubleshooting.md

View workflow job for this annotation

GitHub Actions / Check for Markdown linting errors 

Trailing punctuation in heading [Punctuation: '.']
Possible solutions:

1. Delete Existing Environments: Check if there are any container app environments you no longer need and delete them to free up space.

2. Request a Quota Increase: Request an increase in the limit of container app environments. You can do this through the Azure portal by clicking the help icon (question mark) in the top right corner and creating a support ticket.

3. Review Subscription Configuration: Ensure your subscription is configured correctly and that there are no additional restrictions causing the issue.

4. Use Different Regions: If possible, try creating the environments in different regions to avoid the global limit.

Check failure on line 39 in docs/deploy_troubleshooting.md

View workflow job for this annotation

GitHub Actions / Check for Markdown linting errors 

Files should end with a single newline character