enter image description here
vscode live server is not working. I even clicked use local ip as host in the vscode live server extension settings
Related
I try to create a simply website on a corporate server with static ip:
I open IIS Manager, right click "Add Website".
I set the binding with static ip and port "7878"
Note : This server has already one site that run on port 80
If I open the site directly from server using the static ip (not localhost):
http://{ip address}:7878/
everything work
If i open from any other computer it gaves me timeout error
I have setup a Mean stack on a Digital Ocean Droplet based on UBUNTU 18.
I am using Angular6 on nginx port 80, nodejs on port 3333 which I run on the same machine. I have also enabled CORS on nodejs. The angular application gets build as prod and copied to the server. I have enabled as described on digital ocean the private ip and i can successfully curl the api (nodejs) using localhost, the internal IP and 127.0.0.1
Now the problem: When I am calling the API from the angular6 anything but the domain name is giving me an Error -> Connection Refused, Unknown Error! Locally on my development PC everything is working as It should! I thought it might be a cors issue but I am able to access via IP the remote API from my development machine without any issues. What am I missing? I find it very odd to be able to access it through the domain name and not via the internal IP...
Note that on the development PC angular is running as ng serve... the only difference is that the application is build as prod before uploading it to the remote server.
Angular cant access the private ip because the angular code runs off your browser and not the server. So unless your running the browser right on the server via vnc or something, your local machine cant access the private network (and thus the private ip).
Digital ocean probably recommend you set up a private ip so that you can put your database in the private network so its firewalled off.
Anyhoo, use the FQDN or the public ip in your angular code.
I have established ssh connection. Following that, I have run my node.js application by node app.js on port 3000. It showed console output app is running http://0.0.0.0:3000 port same as my local environment. But when I opened http://external_ip:3000 it is not loading anything. How do I have to run my node app on external ip address
First of all you must have to reserve a static external IP for your VM. If you want to check whether your project is running or not open this following link.
https://[PROJECT-ID].appspot.com
Here is the guide for assigning a static external IP to a VM.
https://cloud.google.com/compute/docs/ip-addresses/reserve-static-external-ip-address
I have just created a simple web server using node server and it's running fine. I can access it from the same PC by going to address http://127.0.0.1:1337.
Now I want to access that web server from my WAN IP. I got my my using whatismyip and got something like 110.36.xxx.xxx.
When I tried http://110.36.xxx.xxx:1337, I got:
Firefox can't establish a connection to the server at 110.36.xxx.xxx:1337.
Here is the screenshot how I created the port forwarding in my router:
What's wrong here?
Localhost is only accessible from the same pc. You have to launch your webserver either on address 0.0.0.0 (it will be available on all network interfaces) or 192.186.0.5 so that it is accessible from your wan interface
I am running a helloworld program using node.js and windows azure sdk.
If I keep : 127.0.0.1:81
This link works and I get the hello world printed on the browser.
But when I try:
--http://192.168.1.6:81/
This link is not working. 192.168.1.6 is the localIP of the machine I am running this application.
Can you please let me know how I can get this working with a IP address
I have the node.js helloworld application from:
http://www.windowsazure.com/en-us/develop/nodejs/tutorials/getting-started/
before I deploy this in cloud I want to run my application with the IP address of the host
The compute emulator specifically binds to 127.0.0.1 and not any other IP addresses, so there's no easy way to do this. (Workarounds like port forwarding are possible, but I wouldn't recommend doing it unless you have a good reason why you have to.)