neo4j connection refused error on centos azure vm - azure

I have installed the neo4j in centos azure vm
I am trying to access it using the my local browser outside the vm. I am trying to create a 3 tier architecture where my neo4j will be sitting in one linux centos vm. But I am not able to access the neo4j.
I have added the inbound rules for ports 8080,7474,7687,7473.
Kindly help me in hosting the neo4j in azure vm. Please let me know what is the issue or configuration needed.
> yum remove neo4j-4.2.0-1.noarch
> systemctl enable neo4j
> service neo4j start
> service neo4j status
curl -v http://ip:7474/db/data
Neo4j.conf
# Bolt connector
dbms.connector.bolt.enabled=true
dbms.connector.bolt.tls_level=OPTIONAL
dbms.connector.bolt.listen_address=:7687
#dbms.connector.bolt.advertised_address=:7687
# HTTP Connector. There can be zero or one HTTP connectors.
dbms.connector.http.enabled=true
dbms.connector.http.listen_address=:#{default.http.port}
#dbms.connector.http.advertised_address=:7474
# HTTPS Connector. There can be zero or one HTTPS connectors.
dbms.connector.https.enabled=true
#dbms.connector.https.listen_address=:7473
#dbms.connector.https.advertised_address=:7473
# To enable HTTP logging, uncomment this line
dbms.logs.http.enabled=false

Related

Can't access Neo4j community version in the browser (installed on a Linux virtual machine in Azure)

I tried to install Neo4j community edition on a VM in Azure, I can't access it in the browser.
I did this:
Created a virtual machine in Azure on which you can host a Neo4j community version server
I choose Linux (Ubuntu 18.04) virtual machine in Azure
Connect to the virtual machine throught Azure CLI and start installing
Installed Java 11 throught Azure CLI
Installed the latest Neo4j community version throught Azure CLI
Setted up Neo4j to be accessible over the internet: sudo vim /etc/neo4j/neo4j.conf
Add/edit the following lines to the config file:
dbms.connector.bolt.enabled=true
dbms.connector.bolt.listen_address=0.0.0.0:7687
dbms.connector.http.enabled=true
dbms.connector.http.listen_address=0.0.0.0:7474
To access port 7474 from outside the Linux machine, I added it to the inbound port rules for the virtual machine (but I'm not sure if I did it wright)
Inbound security rules:
I tried to access to Neo4j in the browser with: http://<ip_adress_of_vm>:7474
But 8) doesn't work: ERR_CONNECTION_REFUSED.
I don't know if it is the best method to install Neo4j community version in a Linux virtual machine.
What do I have to change to succeed in opening this in the browser ? Maybe I did bad 7) ?
According to the messages you provided, the problem is that you do not add the Inbound rules for ports 7474 and 7687 to allow the traffic.

unable to ping DNS server in eucalyptus cloud

I am installing eucalyptus 4.4.4 on centos 7 and i have done all the installation steps but DNS is still not working. When i using ping to check it is showing error that cannot find service.
To check the status of the eucalyptus dns service you can use:
# euserv-describe-services --filter service-type=dns --expert
SERVICE arn:euca:bootstrap:api.10.117.111.14:dns:api.10.117.111.14.dns/ enabled 21 http://192.168.111.14:8773/services/Dns
If the service is not enabled then the most likely reason is that another service is installed and using the dns port.
If the service is enabled then you can check the output using dig:
dig +short ec2.internal #192.168.111.14
192.168.111.14
In this example my dns and ec2 (compute) services are on the same host.
If you see a response such as:
Warning: query response not set
from the dig command then you may not have enabled dns functionality, to check and then enable dns run:
# euctl dns.enabled
# euctl dns.enabled=true
It is also a good idea to review other setting described in the documentation to verify dns settings:
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#shared/setting_up_dns.html

Unable to connect to remote mongodb instance from nodejs deployed on Amazon EC2 VM

I am unable to connect to remote mongodb service deployed using Mlabs. I am able to connect to this service from the node server deployed on my local machine but it does not works when I try to deploy it on Amazon EC2 windows instance.
I have opened the following inbound and outbound rules.
enter image description here
enter image description here
I have also opened the firewall rules for that, but still it does not works.
I am trying to connect to it using mongoose in nodejs.
mongoose.connect('mongodb://user:pass#ds031947.mlab.com:31947/db');
As you said its accessible from your local system so most probably you have your bind-ip set to localhost instead of public ip.
open your /etc/mongodb.conf and make sure the bind ip is set to public access not local host.
run on EC2 instance:
netstat -pl
the output must shows
tcp 0 0 0.0.0.0:27017 : LISTEN 2025/mongod
if it shows localhost:27017 you have to change the config file to make it accessible to public.
Hope it will help !

Cannot list directory on IIS FTP server on Azure, even after configuring Azure inbound rules and Windows firewall

I'am running Windows Server 2012 in Azure, and I've configured the FTP server in IIS. When I try to connect the server, it accepts the username and password and log me in but not showing the directory listing.
I've tried using FileZilla FTP client to connect and it saying the same error.
Status: Resolving address of jothiprakashanandan.southindia.cloudapp.azure.com
Status: Connecting to 104.211.244.241:21...
Status: Connection established, waiting for welcome message...
Status: Insecure server, it does not support FTP over TLS.
Status: Logged in
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I.
Command: PASV
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
Status: Disconnected from server
The inbound rule of Azure is this:
The VM's firewall inbound rule.
However when I try to login from the VM's browser it is working fine and showing the directory list.
In Azure, we should deploy the passive mode FTP, we should add data channel ports range in FTP Firewall Support, then add those ports to NSG and windows firewall inbound rules.
By the way, although the windows firewall seems to allow all traffic that’s required, we also need to enable stateful FTP filtering on the firewall:
netsh advfirewall set global StatefulFtp enable
Then restart the FTP windows service and we should be up and running:
net stop ftpsvc
net start ftpsvc
Here is a similar case, same error as you, please refer to it.
Check which port does the FTP site listen on:
It is usually necessary to restart the Microsoft FTP service after enabling the FTP server rules in Windows firewall to have the change take an effect.
Or restarting a whole machine.
See my guide to Installing an FTP Server on Windows using IIS.
The issue was with Azure network NSG. you need to enable the port range on which data is getting transferred.
Added new rule in NSG to open this port range and it worked.

Unable to Connect Jenkins Windows 10 Slave to Master running

My environment:
Master:
Azure VM running Ubuntu 14.10
Docker (1.9) running Jenkins Image
I have added port 8080 (for UI) and 50000 (for slave) as endpoints on the Azure VM.
Slave:
Windows 10 (running on Mac via BootCamp)
Configured the firewall to allow inbound and outbound traffic on port 50000 (that slave jnlp seems to be using).
I can access my Jenkins Master install over the web. I am trying to configure the slave on my Windows 10 m/c. I have tried all 3 methods to configure the slave.
Each time after several retries, the slave throws the "Connection Refused" error (screenshot attached).
Slave Error Screenshot
Can someone help point me in the right direction? I have little knowledge of Linux systems but proficient with Windows.
I have tried the workaround here but it hasn't worked for me.
There's three things that I think you can check here:
Check that you expose port 50000 on your Jenkins docker container. Check for the Dockerfile, there must be a clause EXPOSE 5000 or something. Or when you run your container run it with something like this: docker run -it -p 50000:50000 which maps local post 50000 to the containers port 50000.
Check that you don't have any security rules on Azure blocking port 50000 to your Azure VM. Don't know about Azure but in AWS you allow port 50000 in your security group(s).
Check your Azure VM's firewall. Is it Windows? Check the firewall and allow port 50000. Is it Linux ? Check iptables and allow port 50000.
Hope it helps.

Resources