Connecting to Node JS Server: Works with Desktops, Not iPhone - node.js

I have a node js server running on my laptop which is connected to my home network via Wifi. I can connect using the IP address 192.168.10.108:8080 on both the laptop running the server and another desktop on the same network (ethernet). However, I cannot connect using my iPhone which is connected to the same network via Wifi.
I changed my script according to results I found while searching for the issue but it hasn't solved my problem app.listen(8080, "0.0.0.0");
I've also tried turning off my Firewall to see if that was blocking the connection but it did not solve the problem.
What else can I try so that my iPhone will connect to the node js server?

Related

How to access express js server from inside local network using no-ip

I have problem ,when I am trying to connect to my express server using host that I have gotten from no-ip. I can't access it inside my router. I have tried my server machine and mobile which was connected to the same network but aslo I couldn't.
But when I tried to connect using mobile data I could access it. how can I solve this strange problem !?

when node js is running in the machine connected to network by wifi can't access it from other devices

When i run this node js code in a pc connected the network by lan (wired) i can connect to this server from other devices on same network, but when i run this servr on pc with wifi connection(same network as the former) i cannot connect to this server from other devices but can connect only from the same pc where the server is running. please help.
const api = express();
api.get('/', (request, response) => response.send(`hello!`));
api.listen(5000, '192.168.1.3', () => console.info('api running'));```
Are you sure the WIFI connection has the SAME IP address as the LAN connection?
(run IPCONFIG at command prompt if you're running a PC)
Did you tried to use the host 0.0.0.0. Once you configured this host you should be able to access the computer using the computer IP.
Usually works, given that most of the time the localhost is not accessible through the ip.

Chrome cannot connect to http://localhost:8080 but http://127.0.0.1:8080 works

This question is similar to the one here, but that question is 18 months old and I have more specific information.
I am running a node.js development server on my local PC (Windows 7), and it is set to listen on localhost:8080.
Using IE11 or Firefox, I can successfully connect to both http://localhost:8080 and http://127.0.0.1:8080
Using Chrome (version 58), I can successfully connect to http://127.0.0.1:8080, but I can't connect to http://localhost:8080 - it gives me ERR_CONNECTION_RESET.
However, if I configure the node server to a different port, say 8081 or 8888, then Chrome can happily connect using localhost as well. So it is not a name resolution problem, but specific to choice of port number.
So what is special in Chrome about localhost when using port 8080?
Maybe this is an IPv4 / IPv6 issue. If your server only listens on IPv4 and you connect to localhost, it could be that it uses the IPv6 address and gets the connection refused.
You could try to start the server on IPv4 and IPv6 to resolve this.
I had a similar issue and found the answer here. I was able to successfully start my project on http://127.0.0.1, but not on any specific port. I had no issues before and all of a sudden I couldn't connect my project on any localhost port, but I had no problem if I used Safari or Firefox. Try running your project in incognito and if it works then you have session running from a project you were testing. Hope it answers your problem if you haven't already.
I had a similar problem, I tried a bunch of things but the only thing that ended up working was resetting Chrome settings. Hope it helps.

NoMachine cannot connect to Debian server, error 138

I can't connect to the KDE GUI installed on my Debian server, using NoMachine. Connection over SSH (Both through PuTTy as X forwarding) works just fine, but somehow I can't figure out how to connect using NoMachine and the NX protocol.
I installed the NoMachine server on my Debian server (nomachine_5.1.54_1_amd64.deb), which seems to work fine. It listens on port 4000. I disabled the firewall on the server.
Then I installed NoMachine on my windows system and tried to connect to the server, using the same IP address as with the ssh connection, and the login credentials I use to login on the server.
I approach the server from another network, using a VPN connection and the HTTP proxy for the network connection.
I tried the tips provided online, but can't get it to work. I still get the error message:
Could not connect to the server.
Error is 138: Connection timed out
Help would be highly appreciated!
You should use the same IP address that is shown in the Welcome GUI like the attached image (taken from the nomachine website)
nomachine welcome gui showing where to connect

Port forward not working to set a local web server

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

Resources