Under Connection | SSH | Tunnels, make sure to configure port forwarding first: (In more human language: forward local port 12345 to the SSH host listening on port 3008, binding to its local 127.0.01:12345 address and port.) Setup port forwarding with Putty Here’s a one-liner if you have an SSH client installed: So we will need to setup some port forwarding so WebStorm can connect to this debugger port that lives in a remote data center. One thing left to do: in our first part, we told Node.js to listen on port 12345 (using the -inspect=0.0.0.0:12345 flag). Once done, we can SSH into our app service using that port 3008 and the credentials displayed on the command line, which is kinda cool (and also kinda irrelevant to this post, but still cool): The Azure CLI tool will create a tunnel between our PC and our App Service on Linux (specified by resource group and web app name), and expose it over port 3008: Make sure to check the prerequisites in this post, and then run this command:Īz webapp remote-connection create -g RESOURCEGROUP_NAME_HERE -n WEBAPP_NAME_HERE -p 3008 Instead, the Azure CLI 2.0 has a command that sets up a private tunnel and exposes SSH. Azure has no way to SSH into an App Service on Linux directly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |