I want to deploy a WCF service that utilizes net.tcp port sharing. When running on a normal Windows Server, I make sure that the NET.TCP port sharing service is enabled and running and my application launches without any issues.
When switching to Azure Service Fabric, this service is not running on the node and my application cannot start. How do I make sure that when I deploy my application to a node that the node has WCF.s NET.TCP port sharing service installed and enabled?
Related
I have a nodeJS application running as a microservice and there are two scenarios:
when a developer is doing development on his machine. nodeJS application should register to eureka service and be able to communicate with other microservices without specifying URL or port to those services
when nodeJS application is deployed to kubernetes cluster, it should not register to Eureka and instead use existing kubernetes Services within the cluster to communicate with other services, again without specifying URL or port, only kubernetes service name
I was thinking of maybe using some env var that will tell the nodeJS service how to behave depending on the environment it is being started in
I'm very newbie on Azure, so I am probably asking a very basic question, please be patient with me.
I have an Azure Red Hat VM and a java Azure App Service Web App, deployed on the same resource group and the same region.
I need the VM to perform RMI calls to the Web App on port 12999.
I've found here that the Azure Web App just exposes ports 80 and 443.
I've also read here that the inbound communication to Azure App Service is possible through Service Endpoints, but it is not clear to me how I should configure the VNet.
Is there any way to have the RMI communication on port 12999 from VM to Web App?
Thanks for the replies.
Is there any way to have the RMI communication on port 12999 from VM to Web App?
No. As you already found, Web Apps only expose ports 80 and 443. Service Endpoints etc. do not change that.
I am wondering, what is the reason for Azure Container instances not to have an HTTPS address?
In comparison, Web Apps do have HTTPS endpoint by default, while Container Instances have just HTTP endpoint assigned.
Why is that?
When you deploy an application to Azure Web Apps, you are basically running your application behind IIS. You can configure the Web Apps platform to terminate SSL connections and all incoming requests received by your application will be via HTTP.
On Azure Container Instances, you container is directly connected to the network. If you want to terminate SSL before it reaches your application, you would need to have a service which provides SSL termination. The typical way to do this without creating any more infrastructure is to run nginx as a sidecar to your application container.
I have an Azure virtual machine, on which a process listens on a certain port. A Node.js application on my local computer is able to connect to this process using the VM's public IP address. But the same Node.js application, deployed as an app service on Azure, is apparently not able to connect using any IP address, despite the fact that the VM allows all incoming traffic on all ports.
(Details: The VM process is running "q" (kdb+), and the Node.js application is using the "node-q" package to connect to it. Both the Azure VM and the Azure app service are Linux, but the local version of the app service is on Windows. The Azure app service is able to connect to my Azure SQL database.)
Any insights into this problem would be appreciated.
There are many reasons for Bad gateway error, probably you could verify these factors on your side:
Azure VM side. Make sure the Azure VM is running and the process port is listening when you request a connection from an application. You could run sudo netstat -plnt on Linux VM to check the listening ports. Or, a server can crash if it has exhausted its memory, due to a multitude of visitors on site or a DDOS attack.
Firewall blocks a request. You should allow all incoming traffic or Azure web app service outbound traffic on this listening port on the VM. In this scenario, you could verify the Network Security Group configuration for the VM and firewall inside the VM if you have. You could find NSG settings by clicking Virtual machine--Settings---Networking---inbound port rules on the Azure portal.
Faulty programming. It seems the Node.js application could work locally.
Temporary issue. Sometimes, there is no real issue but your browser thinks there is one thanks to an issue with your browser, a problem with your networking equipment, or some other reasons. You could refresh your web browser or clear cache and cookies to get the page back what you are looking for. More details you can refer to fixing 502 error.
If you still have any question, feel free to let me know.
It was faulty deployment. I didn't include all dependencies in the upload to Azure. Thank you.
I have a node.js application and a WCF service hosted in a windows service running on the same machine. I need to pass messages from Node.JS app to the WCF service exposed via windows service.It can be uni or bi directional communication. Can you help me to know how to achieve this?
My requirement is to open a communication channel between NodeJS and the WCF service hosted inside Windows Service. My WCF service has net.tcp binding.
I solved by modifying my WCF service and adding another end point for webHttpBinding. From Node.Js application I can access this endpoint of my WCF service.