I have successfully installed one of my application software on the Edge node of my Azure HDInsight Cluster 3.5.
In ideal scenarios post the successful installation of the software, the web page associated with the software can be brought up at port# 8082 of edge node.
However, all my attempts to access http://xxxxxxxxxx.azurehdinsight.net:8082 ends up with the following message "this site cannot be reached".
I have tried to access this port by giving the public ip address of the edge node as well. But it ended up with the same error.
The need here is to be able to access this (http://xxxxxxxxxx.azurehdinsight.net:8082) site from internet.
Thanks in advance for any help !
we got this fixed by creating a sshTunnel (via putty). It seems by default only 22,23 and 443 ports are opened in HDInsight.
Related
I have been having trouble connecting to my virtual machines in Azure since yesterday. So to test I created a new marketplace ubuntu 18.04 image VM and installed nginx, without changing anything.
I expected that navigating to the ip would give me the default nginx website as it usually does but instead it just times out and declares it inaccessible. Nginx is running fine according to systemctl and ufw is disabled as it comes by default in azure images.
Has anyone experienced this before?
As can be seen in your screenshot, Port 80 is not open in your Network Security Group. This is why you are not seeing NGINX.
"DenyAllInBound" will deny all inbound traffic which has not been explicitly allowed by other rules with higher priority.
https://learn.microsoft.com/en-us/azure/virtual-network/tutorial-filter-network-traffic
I have developed website in react and node.js as intermediary to send and receive response.
Now i want to put this on a machine in lab , so everyone can access it.
Can i Install node on machine in lab and run same setup as on my dev machine and give ip of that server?
I tried searching deployment with node js an react, but everyone using AWS, or some external server after npm build.
How do I deploy my react app on lab machine with out actually copying code?
Two Things before you share your IP and PORT:
Have a process monitor setup in your lab machine, Check out pm2. This will help you run your application in the background,
monitor your application and start your application after restart.
Enable port in your firewall for everyone to use. if your lab system is Ubuntu then allow ufw for the port.
Now you can share your IP:PORT and everyone would be able to access it, provided they all are connected to the same network.
If you want everybody access your server, you can share your private IP with them, so others can access it using
yourip:port
I've recently set up a Debian 8 Jessie VM on Google Cloud. I've installed Jenkins and have the service up and running(verified by "sudo service jenkins status"), yet I can't connect to the VM's external IP from another machine. I used to run Jenkins from my personal computer until I decided I needed a dedicated server to run it continuously. When I was running it on my personal machine I would just access localhost:8080 and the Jenkins dashboard would load fairly quickly. However, upon trying to access the external IP address of the VM running Jenkins, I'm usually greeted with "Connection refused" in my web browser.
At the suggestion of most posts I've seen regarding such issues, I've lifted all firewalls on the VM and have tried to ensure that the VM is listening at the correct IP address, but nothing seems to be able to change the outcome presented by my browser. Where does the issue most likely reside: the VM, Google Cloud, or Jenkins? I'm at a loss.
My first guess is a connection/firewall issue. To test this, you could try a port forward using SSH: SSH into your server with a local port forward: ssh -L 8080:localhost:8080 yourserver. You should then be able to direct your web browser at http://localhost:8080/ and your packets flow through the SSH connection. If that makes it work, have a good look at
How to open a specific port such as 9090 in Google Compute Engine . Or better yet, if you are the only one to use that Jenkins server, just keep using the SSH tunnel. It's much more secure than opening jenkins to the public world.
Have you tried installing tcpdump on the VM and doing a packet capture? That way you can determine where the traffic is being dropped. If you don't see any traffic, then it is being dropped somewhere in the cloud before it gets to your VM. If you are seeing traffic, then you need to determine is it Jenkins or some agent on the host (perhaps a firewall but you mentioned you cleared all the rules) ... I would suggest stopping the Jenkins service and then trying to access it again. Do you get the same "Connection Refused" message? If so, then it is something on the VM. If not, then it something at the application layer, i.e. Jenkins.
Happy hunting!!!
I have just installed couchbase 3.0.1 on Amazon Web Services EC2 free RHEL instance (3.10.0-123.8.1.el7.x86_64). The installation was successful and I the couchbase is running on this server.
To access couchbase web console from web browser I need to to use the syntaax http://:8091
unfortunately this is not working. I tried using Public DNS and Public IP both.
For example:
On Google Chrome browser --> http://ec2-54-69-221-173.us-west-2.compute.amazonaws.com:8091
I have also installed the couchbase outside the AWS on VMPlayer. That works fine.
Please let me know is there any additional step I need to take care in case of AWS instance?
Thanks in advance.
I would start troubleshooting this in two ways:
1) Confirm there a couchbase process running on port 8091 on that node using netstat.
2) Make sure you have your security groups for this node set up to allow access to port 8091. If not, add a rule to the security group.
If I had to guess, it is going to be #2 though.
I've just installed Neo4j 1.8.2 onto Azure by following this step-by-step process...
http://de.slideshare.net/neo4j/neo4j-on-azure-step-by-step-22598695
Unfortunately, when I browse to http://:7474/webadmin Fiddler says Error 10061 - No connection could be made because the target machine actively refused it.
I've followed the instructions exactly and haven't received any errors.
Any help much appreciated.
So, I think I got to the bottom of this. I think it was due to the size of compute / VM I was creating. It looks like the problem is caused when running on Extra Small instances. I created a new installation using a Small instance and everything now works :).
Try setting the server to accept connections form all hosts, and maybe use a newer Neo4j, say 1.9.4
http://docs.neo4j.org/chunked/stable/security-server.html#_secure_the_port_and_remote_client_connection_accepts
The way the VM Depot image is set up, it's pre-configured to allow all hosts to connect, and the Neo4j server will auto-start. The only thing you need to take care of, when constructing your VM, is to open an Input Endpoint, with any public port you want (preferably 7474 to stay true to Neo4j) and internal port 7474.
Note that the UI changed a bit since the how-to was published: You can specify the endpoint as the last step before creating your virtual machine. Other than that, the instructions should be the same. And... once the VM is up and running (it'll take about 5-10 minutes), you just visit http://yourservicename.cloudapp.net:7474 and you should see the web admin. Note: this is not the same as your vm name. If you named your VM something like 'neo' then you do not want http://neo:7474 or http://neo.cloudapp.net:7474. You need to use your cloud service name (you had to create a name for the service when you deployed the VM.
I've deployed that image several times in demos, and just tried again right now to make sure nothing wonky happened. Worked perfectly.