Brett, I've tried opening various ports (including all of them!), but nothing seems to make any difference. At the moment, I have open:
22tcp0.0.0.0/0✔4369tcp0.0.0.0/0✔4984tcp0.0.0.0/0✔8080tcp0.0.0.0/0✔8088tcp 0.0.0.0/0✔8091tcp0.0.0.0/0✔8092tcp0.0.0.0/0✔11209tcp0.0.0.0/0✔11210tcp 0.0.0.0/0✔11211tcp0.0.0.0/0✔11214tcp0.0.0.0/0✔11215tcp0.0.0.0/0✔18091tcp 0.0.0.0/0✔18092tcp0.0.0.0/0✔21100-21199tcp0.0.0.0/0✔ This seems to be consistent with the information here: http://docs.couchbase.com/couchbase-manual-2.5/cb-install/#network-ports Cheers, Steven On Friday, 30 May 2014 12:18:59 UTC+10, Brett Lawson wrote: > > Hey Steven, > > It looks like your server does not have the prerequisite ports opened. > What ports have you opened on your firewall? I can't connect to your > server, but any other server works fine, both on and off my own network. > > Cheers, Brett > > On Thursday, May 29, 2014 11:13:49 PM UTC-3, Matt Ingenthron wrote: >> >> Hi Steven, >> >> I just tried it myself and sure enough, I got the same thing. Let me >> ask someone to have a look at it. >> >> Thanks, >> >> Matt >> >> From: Steven Barlow <[email protected]> >> Reply-To: "[email protected]" <[email protected]> >> Date: Thursday, May 29, 2014 at 6:56 PM >> To: "[email protected]" <[email protected]> >> Subject: Re: Client-Side timeout exceeded for operation >> >> Matt, >> >> Is it perhaps possible to get one of the Couchbase JS team to perform a >> quick test trying to hit my server ( >> http://ec2-54-83-43-209.compute-1.amazonaws.com:8092/test) with the JS >> SDK 1.2.4? >> >> As far as I can ascertain, the JS SDK is not working at all after a >> simple npm install (which seems absurd), but I've replicated on multiple >> environments. Is there something about my server instance, or is JS SDK >> indeed broken? >> >> This can be as simple as: >> >> var couchbase = require('couchbase'); >> new couchbase.Connection({ >> host: 'http://ec2-54-83-43-209.compute-1.amazonaws.com', >> bucket: 'test' >> }).stats(function(err, result){ >> if (err) { >> console.log('Error', err); >> } else { >> console.log(result); >> } >> }); >> >> >> Cheers, >> Steven >> >> On Wednesday, 28 May 2014 17:13:47 UTC+10, Matt Ingenthron wrote: >>> >>> Hi Steven, >>> >>> What version of the node client are you running? >>> >>> Did you install libcouchbase directly, or is it the embedded one (will >>> depend on OS to some degree)? >>> >>> Also, with the latest libcouchbase, you can set an environment >>> variable and get additional logging. >>> >>> Thanks! >>> >>> Matt >>> >>> From: Steven Barlow <[email protected]> >>> Reply-To: "[email protected]" <[email protected]> >>> Date: Wednesday, May 28, 2014 at 1:54 AM >>> To: "[email protected]" <[email protected]> >>> Subject: Client-Side timeout exceeded for operation >>> >>> What would be causing the NodeJS SDK to repeatedly respond >>> with: [Error: Client-Side timeout exceeded for operation. Inspect network >>> conditions or increase the timeout] code: 23 for all view operations? >>> >>> I have a test server at >>> http://ec2-54-83-43-209.compute-1.amazonaws.com:8092/test that >>> demonstrates this behaviour. I'm pretty sure I've opened all the requisite >>> ports. >>> >>> For example >>> >>> CURL >>> http://ec2-54-83-43-209.compute-1.amazonaws.com:8092/test/_design/test >>> >>> responds fine, but attempting the equivalent operation using the >>> Couchbase SDK fails as described above. >>> >>> var connection; >>> var config = { >>> host: 'http://ec2-54-83-43-209.compute-1.amazonaws.com', >>> bucket: 'test' >>> }; >>> >>> var couchbase = require('couchbase'); >>> connection = new couchbase.Connection(config); >>> connection.getDesignDoc('test', function(err, result){ >>> if (err) { >>> console.log('Error', err); >>> } else { >>> console.log(result); >>> } >>> }); >>> >>> I can't fathom this at all, it seems to me that the Couchbase SDK >>> simply doesn't work. In fact I've actually managed to bypass >>> the Couchbase SDK altogether (using dscape/nano) and hitting the server on >>> 8092 using regular CouchDB style REST requests, and that works fine. >>> >>> Cheers, >>> Steven >>> >>> >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Couchbase" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> Matt Ingenthron >>> Couchbase, Inc. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Couchbase" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> Matt Ingenthron >> Couchbase, Inc. >> > -- You received this message because you are subscribed to the Google Groups "Couchbase" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
