Amazon EC2 Configuration issues

[Ricburgis]

Hi,

We recently installed Couchbase on our amazon EC2 account, and even though we're able to access the admin console no problem, when we try to connect using a sample node.js script, it gives us a "Client-side timeout exceeded for operation" error, after a bit of googling, apparently it had something to do with closed ports, so we opened up the ports that were needed, along with the buckets ports and it still wouldn't work. 

Then we found a document that said that we had to set the Couchbase server ip to point to the assigned amazon ip address instead of localhost, did that and it still didn't work.

So we're wondering, is there anything we're missing?

[Andrew Reslan]

@Ricburgis

I'm not sure if you are referring to sync_gateway or Couchbase server access issues.

But sync_gateway binds to 127.0.0.1 by default, to get it to bind to an external IP address, you would need to add the following option on the command line

-adminInterface=<publicIP>:4985

This can also be added as a top level property of the config.son file:

"adminInterface":"<publicIP>:4985"

Andy

[Ricburgis]

Yeah, I'm referring to the Couchbase server proper, instead of syncbase access.

[Jens Alfke]

On Sep 25, 2014, at 3:33 AM, Ricburgis <ricard...@allthings.io> wrote:

Yeah, I'm referring to the Couchbase server proper, instead of syncbase access.

You may have better luck asking on the Couchbase support forums, then — I don't think any of us here are particularly expert on setting up Couchbase Server itself. (I'm certainly not; I just know how to double-click the icon on my desktop :)

—Jens

[Ricburgis]

Ok, sounds like a plan, cheers.