I was flowing this guide Quickstart, so i instaled all the things i was supposed to and created ASP.NET on Google Cloud Platform created project.
Then i created VM:
VM
And when i'm trying to publish i have that:
Publishing GcpProject1 to Compute Engine.
msbuild.exe "C:\Users\peter\source\repos\GcpProject1\GcpProject1\GcpProject1.csproj" /p:Configuration=Release /p:Platform=AnyCPU /t:WebPublish /p:WebPublishMethod=FileSystem /p:DeleteExistingFiles=True /p:publishUrl="C:\Users\peter\AppData\Local\Temp\fflssbvg.hc0"
Failed to publish project GcpProject1.
I turned off firewall and i have same versions of .net framework on server and locally.
Help me please to find the solution.
I just face the same problem, the error message from asp.net is short and hard to figure out.
dotnet publish -o "C:\Users\Puzzle\AppData\Local\Temp\v1opor1f.mdb" -c Release
Failed to deploy project HelloWorld to App Engine Flex.
I check other solutions , and find this works for me : https://cloudplatform.googleblog.com/2017/10/4-ways-you-can-deploy-an-ASP.NET-Core-app-to-GCP.html
just use powershell to send command and that works. hope it helps
Related
I have a fully working web api written in dotnet core 3.1. I've been following the TimCoRetailManager series.
The application builds with no errors and works as intended when running in Visual Studio. I have a free azure subscription. I setup a F1 free web app service on linux and two basic SQL server databases, all in the same resource group with the firewall set to allow access to other azure services to connect. I can publish the web api and the databases. I can connect to the databases with azure data studio and things look fine. I updated the config on the app service so it's using the azure secrets instead of my dev environment secrets. The API works as intended when published from Visual Studio, i can get to the swagger ui, and life is good.
On to Azure DevOps. When I use a release pipeline from Azure DevOps, the pipeline gives a success message. However, when I navigate to the API (has a simple MVC landing page + swagger) it just has an "Application Error :(" page. I found the logs on the Azure App service and they have this...
Ok 2022-03-01T21:44:43.8098649 \/ \/ \/
Ok 2022-03-01T21:44:43.8098677 A P P S E R V I C E O N L I N U X
Ok 2022-03-01T21:44:43.8098704
Ok 2022-03-01T21:44:43.809873 Documentation: http://aka.ms/webapp-linux
Ok 2022-03-01T21:44:43.8098757 Dotnet quickstart: https://aka.ms/dotnet-qs
Ok 2022-03-01T21:44:43.8098784 ASP .NETCore Version: 3.1.21
Ok 2022-03-01T21:44:43.809881 Note: Any data outside '/home' is not persisted
Ok 2022-03-01T21:44:44.3985103 Running oryx create-script -appPath /home/site/wwwroot -output /opt/startup/startup.sh -defaultAppFilePath /defaulthome/hostingstart/hostingstart.dll -bindPort 8080 -userStartupCommand 'dotnet TRMApi.dll'
Ok 2022-03-01T21:44:44.4498212 Cound not find build manifest file at '/home/site/wwwroot/oryx-manifest.toml'
Ok 2022-03-01T21:44:44.4499139 Could not find operation ID in manifest. Generating an operation id...
Ok 2022-03-01T21:44:44.4500119 Build Operation ID: 74cf02f2-a6c2-44a8-9077-95f1bab9d974
Ok 2022-03-01T21:44:45.5344493
Ok 2022-03-01T21:44:45.5358264 Agent extension
Ok 2022-03-01T21:44:45.5358438 Before if loop >> DotNet Runtime
Ok 2022-03-01T21:44:46.2152908 DotNet Runtime 3.1Writing output script to '/opt/startup/startup.sh'
Ok 2022-03-01T21:44:46.6953451 Running user provided startup command...
Ok 2022-03-01T21:44:46.7448258 It was not possible to find any installed .NET Core SDKs
Ok 2022-03-01T21:44:46.7453653 Did you mean to run .NET Core SDK commands? Install a .NET Core SDK from:
Ok 2022-03-01T21:44:46.7457829 https://aka.ms/dotnet-download
The build pipeline appears to be working as intended. It produces four artifacts: a folder for the web api with a zip for deployment, a folder for the database stuff notably with a dacpac, and a folder for the front end with a zip file in there, too. The release pipeline isn't publishing all of this though. I set the package to $(System.DefaultWorkingDirectory)/_Standard Continuous Integration Build/ApiDrop/TRMApi.zip.
The release pipeline has the following settings:
Azure subscription: selected free trial and authenticated it
App Type: Web App on Linux
App Service name: selected api's name from drop down
Startup command: blank
Agent Job
Agent: Azure Pipelines
Agent Specification: windows-2019
Artifact download: continuous integration build > selected all artifacts
Deploy Azure App Service step
Task version: 4.*
Connection type: Azure Resource Manager
Azure subcription: read only, prefilled by app service selection earlier
App service type: also read only, prefilled
App service name: also read only, prefilled
Package or folder: $(System.DefaultWorkingDirectory)/_Standard Continuous Integration Build/ApiDrop/TRMApi.zip
Runtime Stack: 3.1 (DOTNETCORE|3.1)
Any tips or suggestions? I'm really scratching my head on this. I'm watching videos on pluralsight and youtube and it seems like the process "just works" for the content creators, but I'm not able to repeat the results.
Edit: Including screenshot of how artifact is configured in release pipeline.
FWIW, I have the exact same problem from the exact same code base.
I also have the build pipeline artifact set up correctly.
I initially got caught up on the message "It was not possible to find any installed .NET Core SDKs".
I went to the app service "Advanced tools" and then used Bash and issued the commands:
dotnet --list-sdks
dotnet --list-runtimes
Initially, it wasnt reporting any sdk's.
This led to me adding an additional Use.NET Core pipeline task at the beginning of the pipeline with the following parameters
Display Name:
Use .NET Code sdk 3.1.415
Package to install:
SDK (contains runtime)
Version:
3.1.415
Compatible Visual Studio version:
16.7.21
Path to Install .Net core:
$(Agent.ToolsDirectory)/dotnet
I chose the above versions which seemed to match what was reported being available on the linux box.
However, none of this seemed to make any difference, as it still fails with the same error as you. I did want to share what I have tried so far, but wasnt enough to solve it.
On a whim, I spun up a Windows-based App server (Free tier) to deploy to as well. I modified my Release pipeline and added a second "Deploy to App Service" step. This second one deploys to the Windows App Service.
Once I did this, the app runs successfully on the Windows App Service after the second deployment step, but not on the Linux app service after the first deployment step.
It turns out the issue was due to a Build pipeline issue.
It was building the API project using a Visual Studio Build (i.e. MsBuild) project step.
In order to target linux, this needs to be replaced with a
dotnet publish (or a dotnet build followed by a publish) with the parameters "-r linux-x64" plus the appropriate output folder.
Build pipelines and release pipelines do not use the same system default working directory. So I think your release pipeline is probably not getting the artifacts in the build pipeline.
There is an easy way to pass artifacts generated in build pipelines to release pipelines:
In your build pipeline, Use publish build artifact task or publish pipeline artifact task to publish your artfact.
In your release pipeline, click "Add an artifact". Then select "Build" as source type and fill in the information about your build. Note the value of "Source alias", which you need to use as the name for artifacts in release pipeline.
Go to the "Azure App Service Deploy" task. In "Package or folder", click browse button, and you can find your artifacts path there.
I'm having a problem publishing and deploying my backend on centos.
First related to publishing the backend. Below attached a picture of the project of my web API.
I am not sure if this is the correct wayI've published them by using this code below:
dotnet publish -c debug -r linux-x64 --self-contained
on each one of the folders except the Test. So I have 3 published projects.
I then transfer it to my centos 7 servers using scp.
Then I open the published OamrBackend.Web server and give permission to the app using chmod 777 ./OamrBackend.Web and then run it.
This is what it shows:
(I am not sure if this is the correct way)
When trying to access this API from my PC it shows a page error This site can’t be reached ERR_CONNECTION_REFUSED.
What was the error here? Is it the way I try to publish is incorrect or they deploy was incorrect?
I wrote this small .net core app that backup and transfer mysql database from a server to a dockerized app. However, when I put it in docker and try to run it nothing happens. If there is an error in the app it should console.writeline the error message but nothing.
FROM mysql:5.7.34
COPY ./dbmover /tmp/dbmover
WORKDIR /tmp/dbmover
EXPOSE 3306
As you already figured out my released .net core app is contained in the dbmover folder and copied on the docker container.
Now if I connect to the container shell and execute the app I get no output of it. I run ./myapp.exe
There are my release settings for my app.
Note that this application is not meant to be dockerized it is just a tool to help build the container.
What am I doing wrong ?
SO I didn't noticed at first but I was publishing with visual studio instead of the command line tool. Once it is done publishing it is ginving you the path of the publish. What I ddin't notive is that it was the parent folder of the publishing folder which was linux-x64 folder. Once I took the linux-x64 subfolder instead of the main one it started working.
I just moved my application to use ASP.Net on .Net Core 3.1. I previously was using NodeJS and Express. I installed the Google Cloud Platform tools for Visual Studio, generated the app.yaml and Dockerfile using the right click menu on my project, modified the app.yaml to what I would assume is a valid configuration, and attempted to publish it. I selected App Engine Flex, selected my project, and I got a "The selected GCP project needs services to be enabled before you can deploy. Enable the services" message. Clicking on Enable the services (which looks like a link) does not do anything. This is preventing be from publishing my app, which is kind of annoying.
Any help would be greatly appreciated :)
app.yaml
service: api
runtime: custom
env: flex
env_variables:
ASPNETCORE_ENVIROMENT: "production"
instance_class: F2
automatic_scaling:
min_idle_instances: 0
max_idle_instances: 2
min_pending_latency: 15ms
max_pending_latency: 100ms
Dockerfile
FROM gcr.io/google-appengine/aspnetcore:3.1
COPY . /app
WORKDIR /app
ENTRYPOINT ["dotnet", "Project Phoenix Game Services.dll"]
Enable the App Engine Admin API.
This happened to me also, when trying to publish a .NET 6 Web API. In order to solve it this is what I did:
Went to my dashboard https://console.cloud.google.com/
Searched for "App Engine Admin API", using the search bar on the top
Enabled it.
I installed the RC1 version of ASP.NET 5.0 on a Windows 2012 Server running IIS. After publishing my ASP.NET 5 application to the server, I try to access the default web page and the web browser hangs (it just clocks indefinitely). Everything runs correctly within Visual Studio. It only does this when I publish it to an IIS server.
I followed the instructions in this lunch to publish and deploy to the IIS server: http://docs.asp.net/en/latest/publishing/iis.html.
Has anyone else experienced this and resolved the issue? If so, what did you do to fix it?
Joel,
I ran across the same issue today, trying to deploy ASP.NET 5 applications to IIS on Azure VMs.
You might not be deploying the DNX runtime with your application, or something is preventing/killing the Kestrel or WebListener process. From what I found, the request hangs because Kestrel (or whatever listener you're running with dnx web) doesn't start, or crashes during the request.
For me, this happened because I wasn't publishing the application properly with dnu publish.
Check the ../approot folder and ensure it has the following directory structures:
../approot
/packages // NuGet Packages
/runtimes // DNX lives here
/src // Your code
If you're missing /runtimes, you'll see the request hang.
To add them, I used the following command:
dnu publish --out <output directory> --configuration <build configuration> --wwwroot <web root name> --wwwroot-out <web root output name> --runtime <either "active" or current runtime> --iis-command web
If this doesn't fix the issue, something may be crashing the application process.
What helped me is to run
dnu restore
command after copying files to the server.
It appeared, that IIS couldn't start approot\web.cmd, I've found that after running web.cmd manually. Then I googled the error and came to this answer