Cannot run the website deployed by Visual Studio - GET http://localhost:8080/_configuration/MyApp 404? - asp.net

I created a new ASP.NET Core Web application in Visual Studio 2019 (.Net Core 3.1, Angular, with authentication of "Individual User Accounts/Store user accounts in-app").
Then I published the application to folder ...\bin\Release\netcoreapp3.1\publish\.
Then I try to test the deployed website
Run MyApp.exe in ...\bin\Release\netcoreapp3.1\publish\.
PS C:\Users\.....\bin\Release\netcoreapp3.1\publish> .\MyApp.exe
info: IdentityServer4.Startup[0]
Starting IdentityServer4 version 3.0.0.0
info: IdentityServer4.Startup[0]
Using explicitly configured authentication scheme Identity.Application for IdentityServer
info: Microsoft.Hosting.Lifetime[0]
Now listening on: http://localhost:5000
info: Microsoft.Hosting.Lifetime[0]
Now listening on: https://localhost:5001
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: C:\Users\wfaaf\source\repos\MyApp2\MyApp\bin\Release\netcoreapp3.1\publish
copy and host \bin\Release\netcoreapp3.1\publish\ClientApp\dist\ in IIS.
The web page shows in Browser. However, the console shows errors?
polyfills-es2015.0ef207fb7b4761464817.js:1 GET http://localhost:8080/_configuration/MyApp 404 (Not Found)
polyfills-es2015.0ef207fb7b4761464817.js:1 GET http://localhost:8080/_configuration/MyApp 404 (Not Found)
main-es2015.faf629d7395bba656bc6.js:1 ERROR Error: Uncaught (in promise): Error: Could not load settings for 'MyApp'
main-es2015.faf629d7395bba656bc6.js:1 ERROR Error: Could not load settings for 'MyApp'
main-es2015.faf629d7395bba656bc6.js:1 ERROR Error: Could not load settings for 'MyApp'
The host of http://localhost:8080/_configuration/MyApp should be the https://localhost:5001. How to set it?

Related

Modeller deploy on a https camunda shared server

We are working in a development environment and have to deploy our dmn definitions via the camunda modeller to our camunda shared server. This server is configured for using only https.
As it is a development environment the certificates are self signed. The deployment with the modeller crashes wit an error message
Deploy error: {"code":"UNABLE_TO_VERIFY_LEAF_SIGNATURE","deploymentName":"XX_isIn","errno":"UNABLE_TO_VERIFY_LEAF_SIGNATURE","message":"request to https://localhost/engine-rest/deployment/create failed, reason: unable to verify the first certificate","type":"system"} [ deploy-error ]
We have imported the ssl certificate into the cacert keystore but received the same error message.

ANCM: Inprocess: 500 error after switching to inprocess from outofprocess mode

When I publish or deploy dotnetcore api's on server it can show the ANCM: Inprocess: 500 Error. when i am switching to outofprocess from inprocess it worked fined. what is the Issue

dotnet publish "Unable to load the service index for source https://api.nuget.org/v3/index.json"

I am getting the error message
Unable to load the service index for source https://api.nuget.org/v3/index.json'
on executing dotnet publish. dotnet restore is working fine with leveraging a local NuGet repository (Artifactory). The system I am running this on has no internet connection. But why does dotnet publish reach out to nuget.org? And is there a way to prevent this happening?
D:\tools\dotnet\dotnet.exe publish proj.sln --configuration Release --output bin/Release/PublishOutput
D:\tools\dotnet\sdk\2.0.0\NuGet.targets(102,5): error : Unable to load the service index for source https://api.nuget.org/v3/index.json[D:\buildAgent_adetca06\work\5a1e5e99f083b612\proj.sln]
D:\tools\dotnet\sdk\2.0.0\NuGet.targets(102,5): error : An error occurred while sending the request. [D:\buildAgent_adetca06\work\5a1e5e99f083b612\proj.sln]
D:\tools\dotnet\sdk\2.0.0\NuGet.targets(102,5): error : The operation timed out [D:\buildAgent_adetca06\work\5a1e5e99f083b612\proj.sln]
My .NET enviroment
dotnet --info
.NET Command Line Tools (2.0.0)
Product Information:
Version: 2.0.0
Commit SHA-1 hash: cdcd1928c9
Runtime Environment:
OS Name: Windows
OS Version: 6.3.9600
OS Platform: Windows
RID: win81-x64
Base Path: D:\tools\dotnet\sdk\2.0.0\
Microsoft .NET Core Shared Framework Host
Version : 2.0.0
Build : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d
Updating to 2.0.5 solved this.

Instal problems , Centos 6, MySql, Tomcat 8

I Have MySql Configured
DB scadabr
user scadabr, pass scadabr
Tomcat8 Running, Examples and Manager all OK
java version "1.7.0_141"
OpenJDK Runtime Environment (rhel-2.6.10.1.el6_9-x86_64 u141-b02)
OpenJDK 64-Bit Server VM (build 24.141-b02, mixed mode)
Scada-LTS.War Download Returns ScadaBR.war file
ScadaBR.War Uploaded to WebApps Folder
Tomcat8 Manager Confirms Running
14-Jul-2017 17:37:04.241 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 23966 ms
14-Jul-2017 17:38:08.939 INFO [http-nio-8080-exec-10] org.apache.catalina.core.StandardContext.reload Reloading Context with name [/ScadaBR] has started
14-Jul-2017 17:38:10.324 INFO [http-nio-8080-exec-10] org.apache.catalina.core.StandardContext.reload Reloading Context with name [/ScadaBR] is completed
404 Error when opening host:8080/ScadaBR/

Publish to Azur fails with 500 internal Server Error

I have a cloud service on Windows Azure, I created a Asp.net WebAPI project and published to the cloud service, that was working fine from Visual Studio to publish before i updated visual studio to update 4 and azure SDK 2.2 to 2.6. But after updating when I publish, I got the following error messages. I tried several times, all failed. Can anyone help me?
even i am not able to publish a new created project on new azure service !
11:00:31 PM - Warning: There are package validation warnings.
11:00:31 PM - Checking for Remote Desktop certificate...
11:00:39 PM - Preparing deployment for TempAzure - 2/12/2014 10:58:23
PM with Subscription ID 'e94e9aeb-7003-4eae-be92-7b7ac0a1ba2c' using
Service Management URL 'https://management.core.windows.net/'...
11:00:39 PM - Connecting...
11:00:39 PM - Verifying storage account 'jasontest'...
11:00:41 PM - Uploading Package...
11:06:48 PM - Warning: The remote server returned an error: (500)
Internal Server Error.
11:11:50 PM - Warning: The remote server returned an error: (500)
Internal Server Error.
11:26:16 PM - Warning: The remote server returned an error: (500)
Internal Server Error.
12:00:27 AM - Warning: The remote server returned an error: (500)
Internal Server Error.
12:05:05 AM - Warning: The remote server returned an error: (500)
Internal Server Error.
12:27:54 AM - Unable to write data to the transport connection: An
existing connection was forcibly closed by the remote host.
After updating from Azure SDK2.5 to SDK 2.6, I had the same problem when trying publish to my Azure service from VS2013: Any deployment effort using Visual Studio fails after some minutes with 500 Internal server error.
As I found the reason is the very slow upload of the Azure package to the cloud - sometimes only between 30kB/s and 50kB/s. The deployment fails because of an timeout which also explains, that the Azure instance logs show no sign of any deployment...
Work around: Deploy from Azure storage
1: Package the Azure solution, either via VisualStudio or via command line:
MSBuild /t:Publish /p:TargetProfile=Cloud /P:Configuration=Release
2: Create an Azure storage container to upload your package to.
Continue using AzurePowerShell cmdlets:
3: Login
Add-AzureAccount
4: Upload the package to the your Azure storage container
$Ctx = New-AzureStorageContext -StorageAccountName "yourstoragename" -StorageAccountKey "yourkey"
Set-AzureStorageBlobContent -File "...\app.publish\yourservice.cspkg" -Container "yourazurestoragecontainer" -Blob "yourservice.cspkg" -Context $Ctx -Force
Determine the PackageURL of the uploaded package.
5: Deploy the cloud service referring to the package just uploaded to Azure cloud storage.
Set-AzureDeployment -Upgrade -Slot "Staging" -Package "PackageURL" -Configuration "PathToYourCloudConfiguration.cscfg" -label "SomeDeploymentInfo" -ServiceName "yourservicename" -Force
(Of course the entire process is scriptable. Kemp Brown wrote a great article: with a script you could adapt to explictly upload the package:
Continuous Delivery for Cloud Services in Azure)
Actually the problem was my network connection.
to identify this problem i created VM on azure with same windows 8.1 OS and same VS. i tried to deploy from there. deployment worked fine. latter I disconnected all other devices from my internet connection and i tried to publish from my machine. it worked !
so conclusion is slow internet connection or may be now we have less timeout time for publish from VS !

Resources