I have created a Web Service API console application in VS, for .NET 6, and specified the ports 6060 and 6061, where I want them to listen:
app.Urls.Add("http://localhost:6060");
app.Urls.Add("https://localhost:6061");
Deployed the application on Linux (Amazon Linux 2).
Then, went to the AWS management console added Outbound rules to open ports 6060 and 6061.
I can connect to ports 6060 and 6061 locally using Telnet, from the same Linux machine, but the ports 6060 and 6061 are still unaccessible from outside.
And, it is not a lag with exposing ports on AWS, because if I run another service on those ports, I CAN connect to them. They are open.
Must be missing something simple and obvious. Did anyone else experience the same problem?
Thanks
Archie
Yes! The suggestion from Lei Yang to change the localhost to 0.0.0. worked! Thank you very much!
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.
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.
New to profiling, I found JetBrains DotTrace as a recommendation by lot of developers. Started testing and ran successfully on Local Machine.
The problem I am facing right now is I am unable to use this for Remote Machine that is hosted on Windows Azure Server 2012. I have followed the instructions mentioned in their documentation provided but no help and getting error like
TCP Error Code 10060
Can anyone help me connect to remote server? Please help.
You need to open an end point in the Cloud Services and your Azure VM to allow the TCP connection from outside world to the DotTrace Remote Agent. One thing you have to remember is to use same port for External Port & Internal port and set it to the port that your RemoteAgent is listening on.
I am working on a project and am attempting to run a FTP daemon on an azure vm running the Technical Preview 2. The Daemon reports that it is behind a NATed router, and as such I can not connect in via another means but the remote desktop connection. (I will be running other daemons on this server as well, and they also have this problem)
I need some way to access this router that my Azure server is behind to configure it to allow for the range of ports that i need to access.
The fine folks at MVA instructed me to ask here, so here I am.
I think you just need to open the port (endpoint setting in the portal) to the virtual machine, so check this article out.
Also, make sure the local firewall isn't blocking that ftp port... I'm pretty sure it's off by default.