I have a problem that i am facing but i didn't found solution in the forum and into elasticsearch official documentation. I have successfully installed elasticsearch 1.7.3 in OVH cloud machin and being able to connect via localhost through the curl localhost:9200. But i tried to connect remotely using http://158.69.78.66:9200/ (where 158.69.78.66 is the server address) without success. Please which configuration am i going to more in order to be able to remotely access elasticSearch in my server.
The attached file represent my elasticsearch.yml actual configuration.
Thanks,
Related
I have Presto installed on my Mac. I also have PostgreSQL. Both are installed locally. I only intend to use them locally. Presto is working fine.
I followed the documentation listed here:
https://prestodb.github.io/docs/current/connector/postgresql.html
connector.name=postgresql
connection-url=jdbc:postgresql://example.net:5432/database
connection-user=root
connection-password=secret
Is there any command I can use in PostgreSQL to get the correct "connection-url". I have been trying the following, but it does not connect:
connection-url=jdbc:postgresql://localhost:8080:5432/MyDataBase
As well, is there a driver I should be downloading? I have been trying for weeks, but cannot get a connection running.
Not sure if this was the only issue you had, but in your connection URL you're specifying two ports i.e. 8080 as well as 5432.
Postgres generally runs on 5432 by default so I think you'd just need:
connection-url=jdbc:postgresql://localhost:5432/MyDataBase
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.
I have created an application using MEAN, After that, I have created the ec2 Linux instance, where I am running this application.I have installed all the dependencies.
Added port 27017 on security group page.
running the command on the ec2 instance as node server.js
Node: My mongo DB is outside my cloud instance i.e on my laptop.
How can I fix this error?
You need to open your laptop to internet which is almost impossible (and you shouldn't). That means you need a MongoDB server which is accessible by your EC2 Linux instance.
You may use a free mongodb hosting such as mlab
On the other hand you can enable another EC2 instance and setup your own mongodb. Beware that you may need to setup firewall if it's not an internal network.
I am having an issue connecting to a rabbitmq server. I can connect to it from the host machine but I cannot get a connection from the container. It used to work before I've upgraded my Ubuntu to 16.04.
Please help.
Got the answer finally. it's a new feature since the version 3.3.0 , It's preventing access using the default guest/guest credentials except via localhost as mentioned here.
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.