deployed Lumen micro services using azure devops and suddenly it started giving 500 internal server error after successful deployment.
Set the same package version on deploying to Azure App Service as the package version that worked locally, for local environment.
App Service runs your app in production mode, so you need to make sure that your project works as expected in production mode locally. Depending on your composer.json, different packages may be installed for production mode (require vs. require-dev).
Thanks, for the answers but I got it fixed by adding flag --ignore-platform-reqs to composer install in yml file.
Related
My firebase hosting deployments have suddenly started failing both in my Github CI Workflows and from my local machine.
$ firebase deploy --only hosting
=== Deploying to '<project>'...
i deploying hosting
Error: Failed to list functions for <project>
The project in question does not have any functions, and only hosts a static site. Google searches for "Failed to list functions" turn up empty, it seems like not a common problem. The only leads I can find indicate some kind of network error.
I have updated my firebase-tools, logged out and in again to generate a new CI token, tried the process from my Github workflows and also manually from my machine, all to the same effect.
I can't find any information about this problem, except that the error seems to come from this part of the firebase-tools codebase:
https://github.com/firebase/firebase-tools/blob/c0f19a32845135108c75a1050024965cb1e3f52d/src/gcp/cloudfunctions.ts
My firebase tools version was 11.14.0. I changed that to 11.13.0. Installed this specific version through npm install -g firebase-tools#11.13.0. After that I could successfully deploy.
I came across the issue. using firebase-tools version 10.5 or upgrading it to blaze plan fixed my issue
I'm running a CI pipeline on Azure DevOps. Part of the release pipeline is deploying a website to our web server (running IIS).
We changed hardware recently and did a fresh install of Windows. Of course I also installed the WebDeploy handlers and everything. But since then, the deployment runs without error, but it doesn't actually update any files. If I publish the website from VS2019, everything is fine.
How would I troubleshoot this?
I forgot to include the new server into the deployment group. Only noticed it when we finally turned off the old server and got the error message that the target was offline.
I've created a Web App with PostgreSQL and Tomcat 8.5 in Azure, and running java 8.
I'm using Eclipse, and have a local version of Tomcat. If I'm running the project locally, I'm able to contact the PostgreSQL. But when I push the project to Azure, I'm getting an error what it can't find the postgre driver.
Anyone have a step by step guide for uploading .jar-files to Azure web apps? I've tried with other projects that don't need postgres, but other .jar-files, and same problem.
you can try publish it using maven. Here are useful links:
https://learn.microsoft.com/en-us/azure/app-service/app-service-web-get-started-java
https://learn.microsoft.com/en-us/azure/app-service/containers/quickstart-java
If the database is also on Azure, you'll need to enable trafic from azure to it: https://learn.microsoft.com/en-us/azure/postgresql/concepts-firewall-rules
I have a web app, and I've setup VSTS to create a package in build, and then deploy it using release management.
It puts all of the result in the wwwroot of the site if I look at it in ftp so I get:
/site/wwwroot/
/wwroot
/
This doesn't run and I get a 404 error.
If I use the URL and go say /wwwroot/images/ it returns it just fine.
The app is set to use .net core and I'm doing a self-contained package.
How do I get VSTS release to put the files in the right place and what is the right place ? I can't find any documentation on this anywhere. Everything is to do with Windows.
Also, what linux target should the dotnet application be set to for self-contained? I have it using ubuntu but I'm sure that's wrong and it's something else.
Please use Azure App Service Deploy task with 4.* (preview) version instead, and deploy again:
I had a similar issue and I responded here. Essentially you need to have a startup command pointing to your DLL because Dev Ops deploys the package in a different way than VS.
Deploying .Net Core to Linux WebApps on Azure with DevOps
I have setup NuGet.Server 3.3+ on Windows 10 IIS
[Working][1]
I can browse already inited packages on the server
When I try and push a known working package to my server
nuget push webgrease.1.6.0.nupkg -Source http://localhost/NuGetSrv/nuget
I get
I get 404
In fiddler the package is sent it looks to be a security issue on the server when it goes to write the file
I have use not network service / classic app pool and also tried admin account for the app pool
Also tried local c:\somedir and a \server\share
I had the same problem :/
If you can get packages but not add
Make sure you have the application pool set to Integrated and not Classic and your network share will work for pushing packages
If you're working on Azure, #HoopSnake's answer still apply, but its worderd differently.
In the App Service => Application Settings => Managed Pipeline Version set this to Integrated.
Atleast, that's what fixed it for me