For some reason my Rocket Hub blocks almost every port except for some of the more commonly used ones like 443, 80, 22, 21, 20, etc.
I can run my local LAMP server on my desktop and access it from my laptop, however when I try to use synergy or connect to a Minecraft server over LAN, I am prevented from doing so. I can access the Minecraft server when I am using the server computer, even using the IP given by the Rocket Hub rather than localhost; but when I try to connect to it through anything else on LAN, I am prevented from doing so.
I strongly believe this is an issue with the Rogers Rocket Hub since I did not have issues before the Rocket Hub. I also have tried adding the specific ports to the NAT Port Forwarding settings but still no luck.
I figured out the issue. The issue is not the router's firewall, it is my virus scanner's firewall - Vipre Antivirus.
I realised this was the issue after trying to start my Minecraft server in Ubuntu, and it worked. The reason why I never had this issue before is because before I got the rocket hub, I hosted the LAN server on Ubuntu.
To anyone who is looking to find a fix, open Vipre Antivirus click on Edit Settings beside Firewall, Click on exceptions, then go to the Ports tab and add the exception for the specific port. In this case, the Minecraft port is 25565 and uses the TCP protocol. Select the exe file for the Minecraft server and you should be fine. If it still doesn't work, you can just temporarily disable the firewall when you want to run the server until you find a fix.
Related
I have just finished setting up Node-red on the a cloud machine hosted with vultr ( Ubuntu 20.04 x64 ) and I am wanting to be able to hit the Node-Red web page but I am failing to do so.
I have setup WireGuard so I can VPN into the machine
I am able to ping the servers Local IP address from my Windows PC
But I am still unable to hit the Node-Red Web Page
Even though Node-Red is running
I am fairly new to working with cloud machines so any help would be highly appreciated.
I'm going to guess that you haven't opened port 1880 for the server.
This could be in one of 2 places
Vultr appear to have their own firewall which you will need to ensure a suitable rule to allow TCP traffice on port 1880 exists. How to configure the firewall appears to be documented here https://www.vultr.com/docs/vultr-firewall-quickstart-guide/
You will need to make sure that the port is open in the Ubuntu Firewall as well. Running sudo ufw allow 1880/tcp should do this.
Overview
Win 10 pro, 64bit
static-server works from localhost
All other node.js servers stop working on localhost,127.0.0.1 and only works on 172.16.xxx.xxx host
From the source I can see that static-server host is 0.0.0.0 which is the same as mine. I run my server on 0.0.0.0 https://nodejs.org/api/net.html#net_server_listen_port_host_backlog_callback
All this happened suddenly on my windows machine and on several web apps with webpack. I installed windows again and the issue persists.
I use WebpackDevServer with host : 0.0.0.0
Details
I'm running on a brand new win 10 with some vpn installed.
So I have these 3 apps
webpack-app on host 0.0.0.0:9080
static-server on port 9080 (should be localhost as well)
webpack-app with react-create-app on port 3000
I start the webpack-app on port 9080 and I go to the browser and says "This site can’t be reached,localhost refused to connect." (I'm 100% sure is running on 9080 because all my webpack apps stop working at once)
I now start static-server and runs on port 9080, doesn't complain at all! Now I go to the browser and it opens the page on port 9080.
So now I think I'm running on 2 different networks. Here is how it looks in windows:
So now I look if somebody is listening to the port 9080 and I see this:
I turn off the static-server and it disappears. Means that the static-server correctly shows up there.
Also there is no other node.exe process over there. So where did my webpack-app ended up?
Now after some times something popups there on port 3000
Not sure why there are so many on the same port, I go to that url and it works. But doesn't work from localhost:3000.
What is going on? why it doesnt work from localhost anymore?
If you use the Windows Subsystem for Linux, especially WSL2, keep in mind that it runs in a Hyper-V virtual machine with a virtual NIC. In other words, it creates its own virtual network.
According to the WSL2 FAQs:
the new architecture uses virtualized networking components. This
means that in initial preview builds WSL 2 will behave more similarly
to a virtual machine, e.g: WSL 2 will have a different IP address than
the host machine. We are committed to making WSL 2 feel the same as
WSL 1, and that includes improving our networking story.
As a result, the development server will run at a different address than 127.0.0.1 (aka localhost). This is why a connection refused error is returned when calling localhost from the browser.
Here is a possible solution, as suggested by Microsoft.
Ran into the same issues as above. Cleared my browser data and cache, it worked like a charm!!
So very strangely after a few restarts it just works. My node.js server listens on 0.0.0.0 instead of 172.xxx.xxx.xxx. I'm really confused as why it works now and why was not working before. If somebody can figure out would be wonderful. Thanks everybody for the help.
Edit: Happened again and I fixed like this: I disabled all my docker and expressvpn apps to start on windows start and restarted my pc, now works.
Edit 2: Happened again and I fixed by closing express vpn and disabling my wifi. I only use the wired Ethernet cable. No need to restart this time.
I think something is going on with my windows machine. Not sure why there are to networks.
I'm trying to host a website in Azure using Phoenix. When I use a browser in the VM to go to the website it works and nmap is also showing that the ports are open.
However, when I go to the website from my own PC I cannot reach it. I suspected this to be caused by the network security group settings so I opened the ports:
However, it still doesn't work. What else can be causing this?
EDIT: nvm I must have been asleep when configuring the security group settings. Thanks to Justin Wood for pointing out the wrong port number.
You already have port 443 (HTTPS) open. You will probably want to open port 80 (HTTP) as well.
I have a node.js website running on my Ubuntu VM. I can access it both from the host and the VM. But if I try http://192.168.10.120:80, from an external device connected to the same network over WiFi, it doesn't work.
What I need to do to make the web site accessible to external devices on the same local network?
I've been googling this for days, and still can't find an answer...
If the host is Windows, there's two things you'll have to do. One is setting up port forwarding in your VM settings. If you're using Virtual Box check this out. Also, depending on your internal networking setup, you may need to allow inbound connections to port 80 through Windows Firewall. Check out this article from Microsoft. The process hasn't really changed since Windows 7 so it should be the same on 8 or 10.
As a side note, security through obscurity sucks but I still wouldn't recommend using port 80.
I am using an android app that streams real-time accelerometer data to the specified ip address of a server. I have written a "server" in C running on Linux which is running in VMware.
I am connected to the hotspot created by the Windows7(Host machine) running the VMware Workstation.
So my question is how do I connect the virtual-machine to same network as the hotspot so that I can get the phone and the "server" program on the same network and stream data to the server program?
I use VirtualBox, but I'm guessing the settings are very similar in VMWare Workstation.
You probably need to do one or both of these things:
1) Port Forwarding. If your app is hitting port 80 (or whatever port), you'll need to tell VMWare that any hits coming in to the host machine on that port get forwarded to the VM. Of course, your VM will have to be listening on that port. I'd suggest using a high port number (over 1024) to minimize conflicts, and avoid annoying root/admin issues using a low port number.
2) Hopefully that gets you there. If not, you may need to change the virtual adapter settings on the VM. NAT mode is a good first try. If not, there are other modes (bridged, internal, host-only) you can tinker with. (Not sure if VMWare uses different names)
That's probably all you need for the topology you describe -- Android device connected directly to the same subnet as the host machine. If not, perhaps your hotspot routes all client traffic to the gateway (i.e. out to the Internet), without allowing direct access to localhost. If so, maybe there are settings for that. If not, ngrok is your new best friend.
It is SUPER easy and allows you to tunnel traffic from anywhere on the Internet to a specific service running on your machine. This would sidestep some of the issues above.
If you want to take your Android device to another network (e.g. cell network), then ngrok is absolutely the way to go, particularly for development and prototyping. This lets you avoid issues with DNS, routing, firewalls, etc.