Skip to content
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

Jump to bottom

Update FAQ to include common failures reasons with links #252

Merged
merged 9 commits into from
Jul 20, 2023
Merged

Update FAQ to include common failures reasons with links #252

Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
1740054
Updated FAQ with common failures in README.md
johnrsanders May 30, 2023
8dc27e0
Update README.md with FAQs failure reasons
johnrsanders May 30, 2023
91bf774
Updated FAQ in README.md
johnrsanders May 31, 2023
9f0d721
Updated FAQ in README.md
johnrsanders Jun 1, 2023
b1c91cd
Update readme with some markdown styling
tonybaloney Jun 29, 2023
b53514d
Update links
tonybaloney Jun 29, 2023
31a3b5e
Merge branch 'main' into main
pamelafox Jul 20, 2023
68c94c7
Update README.md
pamelafox Jul 20, 2023
567f52b
Update README.md
pamelafox Jul 20, 2023
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
14 changes: 12 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,5 +142,15 @@ To upload more PDFs, put them in the data/ folder and run `./scripts/prepdocs.sh

### Troubleshooting

If the web app fails to deploy and you receive a '404 Not Found' message in your browser, run `azd deploy`. If you still encounter errors with the deployed app, consult these [tips for debugging Flask app deployments](http://blog.pamelafox.org/2023/06/tips-for-debugging-flask-deployments-to.html)
and file an issue if the error logs don't help you resolve the issue.
Here are the most common failure scenarios and solutions:

1. The subscription (`AZURE_SUBSCRIPTION_ID`) doesn't have access to the Azure OpenAI service. Please ensure `AZURE_SUBSCRIPTION_ID` matches the ID specified in the [OpenAI access request process](https://aka.ms/oai/access).

1. You're attempting to create resources in regions not enabled for Azure OpenAI (e.g. East US 2 instead of East US), or where the model you're trying to use isn't enabled. See [this matrix of model availability](https://aka.ms/oai/models).

1. You've exceeded a quota, most often number of resources per region. See [this article on quotas and limits](https://aka.ms/oai/quotas).

1. You're getting "same resource name not allowed" conflicts. That's likely because you've run the sample multiple times and deleted the resources you've been creating each time, but are forgetting to purge them. Azure keeps resources for 48 hours unless you purge from soft delete. See [this article on purging resources](https://learn.microsoft.com/azure/cognitive-services/manage-resources?tabs=azure-portal#purge-a-deleted-resource).

1. After running `azd up` and visiting the website, you see a '404 Not Found' in the browser. First, try running `azd deploy`. If you still encounter errors with the deployed app, consult these [tips for debugging Flask app deployments](http://blog.pamelafox.org/2023/06/tips-for-debugging-flask-deployments-to.html)
and file an issue if the error logs don't help you resolve the issue.