-
Notifications
You must be signed in to change notification settings - Fork 649
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.
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
Looking for your backend #523
Comments
It's suspicious that it's looking for the backend at https://localhost:40443/... Do you have a ..\webapp.env file on your machine? If so, make sure that there are NO DEFINITION of REACT_APP_BACKEND_URI in it. Otherwise, you might end up with the problem you are describing. Let me know whether this addresses your issue. |
PR #524 changes things so that even if you do set REACT_APP_BACKEND_URI, deploying to Azure will work fine. |
I can't reproduce the problem on my side... Let me verify the steps you took to get to this problem. First, did you get the latest commits from the repo? Make sure you have the "Make deploy-webapi do all it needs to by default (#524)" change on your computer. Than, did you run package-webapi.ps1 again? |
My steps: 1. Download the latest GitHub library, then import Azure OpenAI and AAD authentication ID, the local execution is running normally. 2. Use the package-webapi.ps1 packager and encounter the above problems after performing deployment to Azure |
Can you check if you've hit the maximum number of indexes? Migration won't be able to proceed unless there is room to create two new indexes. |
#523 (comment) |
This issue has been resolved, thanks |
Once deployed to Azure, it cannot be used
![image](https://private-user-images.githubusercontent.com/49265228/276638350-ecceb9e3-b7cc-49ad-8c70-ba8bc22ff87c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk2MTQ0NjIsIm5iZiI6MTcxOTYxNDE2MiwicGF0aCI6Ii80OTI2NTIyOC8yNzY2MzgzNTAtZWNjZWI5ZTMtYjdjYy00OWFkLThjNzAtYmE4YmMyMmZmODdjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjI4VDIyMzYwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTlhYjJkYTFiZWFiMzUyYTNiZTg2NjZiYzM0Nzk1MDE4NzU3YmRiNDQ3YjI2YzE4OGVmOGJjZGRhMTY5MWYwMjQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.IGDNkTcHMaZr7KTn5CGdPmfHQI4NomKXM6C9xBwqRWM)
./deploy-webapi.ps1 -Subscription {YOUR_SUBSCRIPTION_ID} -ResourceGroupName {YOUR_RESOURCE_GROUP_NAME} -DeploymentName {YOUR_DEPLOYMENT_NAME}
The text was updated successfully, but these errors were encountered: