Point to site VPN connection between a azure web site and classic virtual network using powershell [closed] - azure-powershell

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am trying to create a point to site VPN connection between a web app and a classic VNET. I am trying to see if there is way to automate this using a powershell. But the resources seem to be scarce. Any pointers on this would be helpful

Based on your description, you want to integrate your app with an Azure Virtual Network. Am I right?
You could connect your app to your to your classic virtual network by using PowerShell. Connect your app to a preexisting virtual network that has a gateway and is configured for point-to-site connectivity.
To connect an app to a virtual network, follow these three steps:
Declare to the web app that it will be joining a particular virtual network. The app will generate a certificate that will be given to the virtual network for point-to-site connectivity.
Upload the web app certificate to the virtual network, and then retrieve the point-to-site VPN package URI.
Update the web app's virtual network connection with the point-to-site package URI.
More information please refer to this link.
Also, you could do it on Azure Portal. More information please refer to this link.
Notes:To enable integration simply click on the VNET you wish to integrate with. After you select the VNET, your app will be automatically restarted for the changes to take effect.

Related

How to open server Port for public so that i can access my locally hosted NODEJS server [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
MAKING THINGS SIMPLE EDITS
I am developing an app, have a nodejs API that read data through MSSQL server, now that API is Running on Localhost:3131/ It means it will run locally only.
I do have a Windows Server that stays online always, I can use pm2 on that server with the API files to make things Live, But if i run it how can i make my SERVER IP Public so I can access it through everywhere.
HOW DO I MAKE MY SERVER IP ONLINE BUT SECURE!
There are many ways to achieve what you desire. If you were to do it on your own network/pc then one traditional method called 'port forwarding' can be used for projects under development, but this still means that your IP will be exposed to the web.
Virtual Private Servers and Dedicated servers are used more commonly used these days to host powerful applications. You would need to run a web server first where your web files can be hosted and then you can link your node.js server and sql database.
There are several hosting providers out there which are built for nodejs applications. You can go for 'unmanaged' and 'managed' hosting providers.
Managed providers provide a simplified "Node Appliance" solution. Node and NPM will already be set up for you, and deploys are typically done via git push or similar method. You will have less control of your server, but everything will be set up for you.
There are some managed hosting providers which nodejs recommend themselves. You can view them here:
https://github.com/nodejs/node-v0.x-archive/wiki/Node-Hosting
Some popular ones include:
Heroku
Amazon Web Services
AppFog
Microsoft Azure
RedHat OpenShift
In your case, you are using SQL and Node, so Heroku actually offers free nodejs hosting and provides a free addon for MySQL databases too. Only downside is that the duration (hours) for which you can run apps are limited.
It might be worth doing this on a Virtual Private Server for lower costs. Alternatively, have a look at NodeChef who specialise in Node.js and MySQL.
Hopefully, this gives you enough information to understand what steps to take next.

No connection could be made because the target machine actively refused it 127.0.0.1:10000 [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
So I've been getting this error when I run my program, an F# web app, on my laptop, but not when I run it on my desktop. I know it has something to do with the firewall ports, and I've opened the port my web app uses, but for some reason I still get this error.
The web app is a simple Owin api with SPA front end, and it's meant to get data from my SQL Express database.
When it runs, my web app, is hosted on iis express and I've set it too port :1337. I've done a netstat -a to see all the ports, 1337 is set as listening, while :10000 isn't listed.
Any ideas?
The IP address 127.0.0.1 is always a loopback port and is the same as "localhost". So you can't access that IP across a switch, a router, etc.
Find out the actual IP address of your desktop (where I presume your application is) and try to access it that way. For windows, you can do run "ipconfig" at the command prompt. For Linux you can run "ifconfig"

how apache web server works [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
Hi I just finished setting up my new apache web server from my laptop running windows 7. I created the server using apache, then port forwarded my laptops ip (port 80), and finally got myself a free domain using dot.tk. Ive added a few files and done some basic html stuff, and it is successfully up running and accessible to everyone through the domain. But i have a question. Lets say someone was to download files from the site. Is my local network's bandwidth consumed? If anyone can explain how this works that would be great.
Thanks in advance.
The data will run through all segments connecting the client (your end user) to the host (your hosted web server).
So if they need to get to your house where your laptop is to get to the web server, then your house's network connection's bandwidth will be used.
If you hosted it remotely on some shared server site like Amazon instead, then the bandwidth of remote clients accessing your server never uses your home connection's resources, it only uses the resources between their computer and Amazon.

Allow SSH for a Hosting Customer on VPS Server? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have a VPS server and a client is asking for SSH access on their hosting account.
I can allow this through the user setup for that particular account but will they be able to admin the entire server then?
I am worried their developer might start installing modules and break my other clients' sites.
Does your VPS come with any control panel ? If so, its usually safe to allow SSH access. However, here is what I would do.
Find out why the client wants SSH access. This is not a conclusive method but would give you a chance to provide alternative solutions if you are uncomfortable enabling SSH access. Note that a lot of hosting service providers, small and large, do not allow SSH access (atleast not without making it so hard that the casual client refrains from asking).
For your mental comfort, create a SSH account for yourself and login with SSH access. Try to see what you can do beyond that specific account. If your test SSH access does not allow you any access beyond that test account, you know that the other guy cant do much either.
you can allow your client to access SSH. It will not create any problem for othersites which is in the same server. As you are giving them only the user account they can not execute root commands. However if the client want to install any modules they need the root authentication.

Windows Server 2008 SSTP VPN in a Non-Domain Environment? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
Is it doable to set up a non-domain-based (standalone) Windows Server 2008 as an SSTP VPN (Secure Socket Layer Tunneling Protocol VPN)?
I'd like to enable remote users to access a network via SSL-based VPN (currently using PPTP) by making an SSTP VPN connection via a Win2k8 server. Most of the docs seem to include running in an AD domain with an in-house Certificate Authority to enable this feature.
Is it possible to do this with a stand-alone Win2k8 server? If so, how?
you connect with host address for sstp. you can use standard web certificate from any ssl cert provider. that host address need to resolve to your vpn server.
step-by-step guide
http://www.windowsecurity.com/articles/Configuring-Windows-Server-2008-Remote-Access-SSL-VPN-Server-Part2.html
My understanding is that the certificate used as part of the authentication hasto come from Active Directory Certificate Services, and there is no way to get it from any other source (I'll admit to not trying too hard to figure out if it was possible, I was investigating SSTP for another VPN related project)
Setting up the 2008 server as a standalone AD controller would get around the issue; the client systems don't need to be in the domain.