Cannot connect OpenStack VM - node.js

I have 116.89.189.0 public ip and in openstack vm, it allocated 116.89.189.39.
And I installed nodejs on vm(ubuntu 18.04) and started basic server.
but it doesn't works. what strange is that i can ping to 116.89.189.39 but
with my pc browser, 116.89.189.39:3000 doesn't works.
I checked with wireshark, there are many TCP Retransmission packets and
some strange packets from 116.89.189.3 (NOT 116.89.189.39)
below things are my nodejs server example and sercurity groups settings.
security group setting
network topology at OpenStack
nodejs on ubuntu
basic server source code

Related

Microsoft Azure, issue with open ports

Currently hosting a microsoft azure server that has a SCP: Secret laboratory game server on it.
OS: Ubuntu 20.04
After setting up the server and downloading the server files, I can't seem to connect to the server. The port that is needed for the game server is 7777 and I have the port open under NSG with UDP and TCP protocol, but after using multiple port checkers and trying to connect in game, I always got the port closed answer or was given a connection error.
I have tried using the azure's own troubleshooter, but that says the ports are open. Tried different ports like 7778 or 7779. Checked the firewall, but I dont even have it enabled.

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

Can't access basic Hello World application launched on Amazon EC2 windows server using NodeJS

I tried to look for solutions and most of them talk about adding HTTP, RDP, HTTPS to security group which I have already done. I have a basic hello world nodeJS application running on Amazon Windows Server 2012. I want to access this application using DNS but it's showing ERR_CONNECTION_TIMED_OUT in my local laptop browser.
Configuration:
I have RDP, HTTPS, HTTP, SSH, Custom TCP Protocol with 9000 port (nodeJS is running on port 9000) for inbound rules and for outbound default "All traffic" rule is present. I have not done any changes in the Windows Server 2012 configuration. WHen I run localhost:9000 in the windows server 2012 then server returns "Hello World" but when I try that on my local machine with DNS : 9000 then it says ERR_CONNECTION_TIMED_OUT
Thanks for everyone's support. Special thanks to Viccari. His suggestion (in the comments below the question) worked. I needed to add the port to the firewall. So basically after adding all the protocols to the security group, I had to add the new port on which the NodeJS is working, to the firewall in the server. Finally its working.

Azure User Defined Endpoint at Ubuntu not working

I got a problem with Azure Endpoint using Ubuntu.
SYMPTOMS
Online port scanner reported that port 1194 is closed even though the End point was defined to be open at Azure Web Interface for that VM
SETTINGS:
UFW, aka Ubuntu Firewall is inactive.
No IP Table was defined in Ubuntu
On Azure web management interface, endpoint called VPN, port TCP 443 and UDP
1194 was set to open, bidirectional allowing direct return. Public and Private port is both 1194, and both 443
lfor and netstat on ubuntu reported thata service is listening on 1194, got NC to listen to 443
DIAGNOSIS
From Ubuntu, I can see the internet. Pinging Google, getting updates works fine.
I can remote into the machine using default port 22, which is a default open endpoint defined by Azure Ubuntu Image
Restarted Ubuntu everytime a setting change.
Tried deleting and re-creating Endpoint rule, failed
Tried shutting down the VM, and delete and recreate endpoint rule, failed
I CAN Telnet to my local host from Ubuntu via 443.
TROUBLESHOOTING STEPS DEFINED
From my local computer, unable to telnet to the Ubuntu server via 443. Ok on 22, terminated because of protocol mismatch, but that is of course fine.
Online port scanners all report that 1194 was closed and so is 443
Some help would be appreciated.
I think that you need to manually configure the endpoint.
Please check https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-set-up-endpoints/?rnd=1 for more information.

I can't access my Hyper-V Linux Web Server over the Internet

I'm trying to access a VM Linux Web Server from Internet but as response I get the server's internal IP.
Infra:
Physical PC: Windows 8 running on IP x.x.x.10 (internal) and y.y.y.y (external/internet)
Virtual Server: Debian 7.3 + Apache2, running on a Hyper-V machine, IP x.x.x.11
Router: D-Link DMG-6661 with 'Applications' and 'Virtual Server' set on both :80 and :7080, pointing to x.x.x.11
Inside my network everything works fine, I'm able to access my web page using both x.x.x.11:80 and x.x.x.11:7080.
Outside my network, lets say at work, if I try to access y.y.y.y:80 or :7080 I get ERR_NETWORK_ACCESS_DENIED and the address on my browser changes to x.x.x.11!
What am I missing here?
Thanks.
So difficult to answer you without precisions... Please check all network segments and software/hardware components ( linking your web browser at work to your Apache server). Lot's of thing may drop your connection. Think about these questions:
Does your router allow incoming connections from the Internet ? Is it configured to NAT/PAT incoming traffic to your Web server at x.x.x.11:80 ?
Does your Linux VM allow connections from other network than your LAN (netfilter/iptables configuration ?).
Does your Apache is configured to accept incoming traffic from any IP addresses ?
Regards

Resources