Note: I am new to Azure.
I have created "Web App" using nodeJS 14.16, created docker "linux" container (FROM node:14.16 AS build) and published to Azure Web services, it works fine.
But on the security side (Security Check) I am getting lot of errors like below:
"Debian Security Update for gmp (DLA 2837-1)" "Debian Security Update for libwebp (DLA 2677-1)" "Debian Security Update for nss (DLA 2836-1)".
TBH, I am not sure where these errors comes from and how to resolve these errors. Even I have not used these packages in my nodeJS application. Could anyone please give me an idea or provide any thoughts to resolve this issue.
It looks like you have Microsoft Defender for Cloud: Defender for Containers enabled for your subscription. Defender for Containers includes an integrated vulnerability scanner for scanning images in Azure Container Registry registries.
https://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-containers-introduction?tabs=defender-for-container-arch-aks
In your question, you say you are using NodeJS 14.16 which it looks like needs to be updated to 14.16.1. Once you push a new version to your ACR, Defender for Containers should rescan you repo and clear this findings in a couple hours.
https://nodejs.org/en/blog/release/v14.16.1/
Related
In order to avoid doing some overhead work, I decide to use a work-around to upgrade my VM from server 2016 to 2019. The work around was successful and everything is running fine. One hiccup though is that I still see the plan being set to "2016-Datacenter".
(Correct me if I am wrong) So far doing some digging I see that this is set at the create time of the VM; it corresponds to the sku of the image used to build the VM.
My question is, are there any gotchas if the VM is running server 2019 but the plan is set to "2016-Datacenter"
Plan information is metadata Microsoft uses to track Marketplace offers. If you want to create an image in a shared gallery, using a source that was originally created from an Azure Marketplace image like this, you may need to keep track of purchase plan information. You may face issues when you create a VM from the Azure Marketplace image if there is wrong plan information. Read here for more details.
We are able to do an Azure VM in-place upgrade to Windows Server 2019. Here is the step by step process to update the IaaS VM Windows server to Windows Server 2019 for your reference.
However, it's not recommended to do because Microsoft does not support an upgrade of the operating system of an Azure VM.. It prefers to use a clean uninstallation and installation. To work around this issue, create an Azure VM that's running a supported version of an operating system, and then migrate the workload.
Iam trying to create a Ubuntu server lab using Azure Lab Services account and followed the below steps.
In , I have already enabled the Ubuntu Server 18.04 LTS in Lab Services – Marketplace images.
In , enabled marketplace image is listed in lab setup page
In , Error: The gallery image 'ubuntu server 18_04 lts' must be enabled for programmatic access in this subscription.
Can anyone help me how to resolve this error - "The gallery image 'ubuntu server 18_04 lts' must be enabled for programmatic access in this subscription."
Also, there is no option like "Want to deploy programmatically?" on the Ubuntu marketplace image page, attached the screenshot below.
I checked myself and have the same problem with Ubuntu 18.04LTS and 16.04LTS. However it works with Ubuntu 19.04 or other Windows images, so it seems there are problems with those images in Azure
I'd suggest you raise a ticket from your subscription or contact them via twitter #AzureSupport. Meanwhile, You may use that Ubuntu 19.04 if it works as a workaround
You can try these links:
From portal (https://azure.microsoft.com/en-us/blog/working-with-marketplace-images-on-azure-resource-manager/) you'd need to go to the image in marketplace and enable it for the subscription you're using looking for the "Want to deploy programmatically?" option (maybe you have more than one?)
From CLI or PowerShell you might try this: https://blog.turtlesystems.co.uk/2018/10/16/Enabling-Programmatic-Access-in-Azure/
Thanks again Bhanu for surfacing the issue. Our Internal product team was already working on fixing the issue.
The issue should be resolved now, you should be able to create the VM's in the lab with Ubuntu 18.04LTS/16.04LTS images.
I am trying to use ABCpdf .NET with Azure App Service and getting the following error when generating a PDF.
Unable to render HTML. Failed to configure IE 9 or above for the MSHtml engine:
Access denied while writing to the registry.
For IIS applications, please enable "Load User Profile" or
consult MSHtmlBootstrap in the documentation.
Usually in a VM I would set Load User Profile to True and it works but in Azure App Service, I do not have access to IIS Application Pool configuration.
According to the developer of ABCpdf, it should work with Azure websites.
http://www.websupergoo.com/support-azure-abcpdf.htm
Windows Azure Web Sites
WAWS sites operate as 32-bit processes in a multi-tenanted environment. In order to isolate one site from another WAWS is locked down to prevent inter-process communication. While you may find ABCpdf (32-bit) will install to WAWS, we expect the functionality will be diminished.
You cannot modify the registry with Azure Web Apps (formerly Web Sites). So, you're getting an error because the app cannot register itself. Being a multi-tenant service, you are not allowed to make registry modifications.
You need to go back and look at that page again, where they suggest using a VM or a web/worker role (both of which do allow for registry modification).
Even though this is a few years old it's the top StackOverflow question for "ABCpdf App Service" so it seems pertinent add an updated answer.
As of version 12.1 ABCpdf.NET includes the ABCWebKit HTML rendering engine based on WkHTMLToPdf 0.12.6 (Qt patched version).
Although limited compared to the default ABCChrome engine, it will enable rendering in a 64-bit Azure App Service on Windows using Basic App Service plans B1 and above.
NB: it will not work on any of the free App Service plans, or on 32-bit instances.
More information:
Updated ABCpdf .NET Azure Deployment Guide for App Services
Example project on GitHub
I am looking at migrating a dotnetnuke website to Azure. I need both staging and production versions of the site to be running.
I have looked at using Azure Websites, but at the moment there is no support for SSL on custom domains so this can't be used for the production website. I have migrated the staging site to an Azure Website and now have numerous options for publishing updates (ftp, git, using web matrix).
Due to the constraints of Azure Websites, I used the DNN Accelerator to create a cloud service for the production environment. This set up will allow me to have control over IIS and therefore manage SSL certificates (I think).
The problem I have with this is there does not seem to be any publishing options. The only way I can publish is by connecting to the Azure instance via RDP and then copying the website files onto the files system.
Are there any other ways of publishing? I have looked at converting the website to a WAP, but I believe this has implications when it comes to updating to new DNN versions.
You should never publish your application through RDP since these changes are non-persistent (meaning what you published might disappear after a hardware failure / ...). Adding new instances would also mean that these instances don't have the files you published before.
I suggest you start by looking at the DotNetNuke Azure Accelerator first. If this doesn't fit your needs you might always try to build something yourself, but if you want to say with a regular website and not a web application I wouldn't count on Visual Studio support. In that case you might want to look at creating a package from the command line and using startup scripts to add your website in IIS.
Sounds like you need to use a Start-up task to install the files in the correct place for a Web Role (Cloud Service) Smarx has a nice overview here, MSDN has a wealth of info too http://blog.smarx.com/posts/introduction-to-windows-azure-startup-tasks
Another option is IAAS for Azure with a persisted VM, more work mind you, Cloud Service would be the most efficient and correct solution...
I already have an application on App Store. I'm now finishing the LITE version of this application. The way I created the LITE version was to copy the FULL version project and change the relevant features so they match what I want to have in the LITE version. I also changed the Project Name (from "AppName" to "AppName Lite"). I also created in the Provision Portal new App ID, Provision and Distribution Profiles, downloaded the Certificates and dropped them on the XCode icon.
The LITE version runs perfectly on Simulator and on Device. Now I wish to create this ipa file so I can upload it via Application Upload. but... I get an error saying: Code Sign error: The identity 'iPhone Distribution' doesn't match any identity in any profile
If anyone had simliar scenario, please share what you did to solve it.
If anyone knows of a good TUTORIAL explaining all the related steps required to upload an App to App Store (and please please please don't share a link directing to Apple Provision Portal, following it caused all the confusion I have now), maybe something that also explains the rational behind their long-weird-unintuitive process.
thanks...
The error means, you do not have certificate which is referred from your distribution provisioning profile.
You should create new certificates and provisioning profiles. i.e..
Create new Certificate Signing Request and proceed with creating certificate for distribution and provisioning profile. This should validate your binary.
Hope this help, please ask if it does not.
Zain Syed