I have the downloaded application largely unmodified but known working on local instance Followed https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Deployment-Angular-Publish-Azure for a split application and having errors
Error in console:
Default levels
GET https://azure-publish-demo-server.azurewebsites.net/AbpUserConfiguration/GetAll?d=1576866925084 500 (Internal Server Error)
abp.js:342 WARN:
abp.js:342 Could not find localization source: AbpWeb
Error in App/Log/:
WARN 2019-12-20 16:48:12,915 [8 ] Abp.BackgroundJobs.BackgroundJobManager - Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
---> System.ComponentModel.Win32Exception (2): The system cannot find the file specified.
…
Top portion of appconfig.production.json:
{
"remoteServiceBaseUrl": "https://azure-publish-demo-server.azurewebsites.net",
"appBaseUrl": "https://azure-publish-demo-client.azurewebsites.net",
"localeMappings": {
"angular": [
{…
appsettings.Production.json:
{
"ConnectionStrings": {
"Default": "Server=tcp:azure-publish-demo.database.windows.net;Database=AzurePublishDemoDb;User ID=admin;Password=mypassword;"
},
"App": {
"ServerRootAddress": "https://azure-publish-demo-server.azurewebsites.net",
"ClientRootAddress": "https://azure-publish-demo-client.azurewebsites.net",
"CorsOrigins": "https://azure-publish-demo-client.azurewebsites.net"
}
}
Originally having issues where the console was saying CORs errors so I went on both client and server Azure resources and set Enable Access-Control-Allow-Credentials to enabled
2 Answer(s)
-
1
What is the content of your api application's web.config file?
I guess the api application's environment might not be Production
-
0
<environmentVariable name="ASPNETCORE_ENVIRONMENT" value="**Development**" />
we moved to a different hosting platform and it resolved the issue but I think you were right in pointing out that the API was built incorrectly I think there may have also been additional routing issues within Azure portal itself