Azure web roles locally start on the wrong port - azure

I have a simple web application which we recently moved over to Azure. Running in the local Azure emulator and on IIS Express, in the WebRole I have set it to run on https://localhost:12345, but when I run the project it comes up on http://localhost:63855/. Completely different port and a distinct lack of HTTPS.
Thank you in advanced,
Andrew

Related

Is a node.js app running on express.js hosted in Azure using IIS?

I'm working on a app that is hosted in Azure.
The app is a web-app based on node.js/express.js.
Is it running on/in a IIS server since it is hosted in Azure?
My app does not use the iisnode package. But i wonder if it is inherently running on IIS since it is hosted in Azure?
Also: As i understand at the moment, IIS-express and express.js is two completely different environments for hosting web-servers.....?
Just according to your description, it seems that you were talking about hosting a node App based on express.js to Azure WebApp for Windows.
Yes for hosting Node.js app in IIS on Azure WebApp for Windows, you need to use iisnode (a native IIS module) to host node.js applications with the web.config file in IIS on Windows. For more details, you can refer to the wiki page iisnode wiki of GitHub repo Azure/iisnode to know what iisnode is, and to know how to host it with a web.config file in IIS via the other wiki page Using a custom web.config for Node apps of GitHub repo projectkudu/kudu.
However, No for Azure WebApp for Windows, because you also can use IIS as a reverse proxy server to handle a Node app via the default port %HTTP_PLATFORM_PORT% specified by Azure WebApp like the blog Running java jar file to serve web requests on Azure App Service Web Apps for Java said. But generally, it's not a recommended way.
Meanwhile, No for hosting Node app on other Azure services, such as Azure WebApp for Liunx, Azure VM, or Azure Container services, these services based on Linux do not require IIS, so the iisnode module also be not absolute required.

Trouble exposing port on Azure Container Instance

I want to deploy a .Net Framework application to ACI that has a web frontend. The programm is set to start the web service on port 8090, so I entered that in the "ports" section of the ACI setup and set a DNS name label. As far as I understood it, this should be enough to make the website publicly available, but I get the "Website not available" error message.
I ran the container locally and it works just fine. I also added the EXPOSE command to the Dockerfile, but that didn't help either. The image is based on a .Net Framework Windows Server Core 2016 image, which should work with Azure.
To anyone seeing this in the future: It seems you can only expose web interfaces on port 80.

Azure VM (Not Classic) - Cannot deploy website using Web Deploy from VS 2013

I'm getting a time out error in VS Publish Web module when trying to validate my http connection to our Azure VM. I'm simply looking for a better way for our small dev team to deploy our MVC website to the VM other than publishing to file or publishing to FTP.
I've got Web Deploy on our Windows 2016 server, and the proper
services are running.
Remote Service is installed with Web Deploy.
Port 8172 is open and I am able to connect using Telnet from my
remote box.
I updated the pubxml file with:
<AllowUntrustedCertificate>True</AllowUntrustedCertificate>
<UseMsDeployExe>true</UseMsDeployExe>
<UserName>un</UserName>
<Password>pw</Password>
Not sure what else to try at this point, but this has been a PITA to say the least. Thanks for any input! FYI - This is not Azure Classic.
Screenshot of Error

Test Win8 App hosted in Azure Compute Emulator on Tablet

I have a two web application in Visual Studio 2012 running in the Windows Azure Compute Emulator (using IIS Web Service, not Express). Additionally I have a Windows 8 App in another Visual Studio instance which uses both azure web applications. This combination works fine on the same machine.
For presentation purposes I'd like to run the app on a Windows RT Tablet. Therefore I use the remote debugging tool to run the app on the tablet. Running the app is not the problem. But I didn't found a possibility to connect to the web applications from the tablet. The azure Emulator generates URLs like 127.0.0.X:81 but the tablet cannot resolve this address.
Is there a workaround to solve my problem? A way to run the azure application with the IP address of my dev machine? Or is it possible to create a kind of a proxy running on the dev machine which forwards requests from the tablet to the azure application?
I've seen a possible solution running fiddler as a reverse proxy. This does not work for me because fiddler seems to listen only on one port. But I need two.
Another possibility would be to configure the Azure Emulator endpoint.
Take a look at this SO answer for more information.

Access Azure Development Server From VM?

We are developing an application that we are deploying to Azure. It needs to work with a specific machine configuraiton. We we have this configured as a VM which developers can run locally.
However to test the VM configuration we need to publish to Azure and access it on a live Azure instance. Is there anyway to allow a local VM to get access to the Azure environment IIS on the developers machine? It doesn't seem to show up in IIS Express so I guess it isn't the same as a normal site?
Also is it possible to configure an Azure environment locally for testing. We want to host test applications for internal use and don't want them run on developers machines. We would like to run them on a server in the office.
Any ideas?
Thanks
I think that the answer to this question will outline the general guidelines you could follow to enable your environment.
Windows Azure Emulator has its own load balancer simulator which bind to socket 127.0.0.1:81 (most of the cases, if port 81 is free). If the Azure project is developed with Azure SDK 1.3 or later with Full IIS enabled, then the Azure Emulator (for versions 1.3 ~ 1.6) will use local IIS to host the sites. IIS Express is not involved in any way with the Azure project. If you happen to run IIS Express, then most probably you have set up your web application project as a StartUp project in the solution. The correct way to locally debug Windows Azure applications is to use the Cloud Project as a startup project.
Please kindly update your question, if there is some doubt or confusion after checking the mentioned related question.

Resources