Couchbase 4 CE Node.js SDK 2.1.6 prebuild AWS Setting Couchbase hostname to anything other then 12.0.0.1 causes “An unknown N1QL error occurred” in Node.js when using n1ql query, but queries work in Query Workbench. if you set it to 127.0.0.1 then join a cluster I get “An unknown N1QL error occu…

Hi Cihan, I found the solution. I was connecting to the servers using the public DNS, but the servers were named using the private IP. This caused issues when using N1QL. Since I am using AWS, I created an internal hosted zone, and assigned a domain name to each server which I use in my connection…

Setting Couchbase hostname to anything other then 127.0.0.1 causes "An unknown N1QL error occurred" in Node.js using n1ql query

Node.js SDK

cihangirb May 20, 2016, 5:46pm 2

Hi @rdt_sd,
is this a single node deployment or a cluster deployment?
thanks
-cihan

Topic		Replies	Views
An unknown N1QL error occured. This is usually related to an out-of-memory condition. CouchbaseError: DNS/Hostname lookup failed Couchbase Server	8	2530	September 14, 2017
N1QL not working on Node js in AWS Node.js SDK query , n1ql , node	1	1610	November 2, 2018
Unable to connect N1QL engine to Couchbase / node.js driver SQL++	3	4471	April 4, 2015
n1ql query causes error node.js Couchbase Server	3	2291	September 25, 2015
An unknown N1QL error occured. This is usually related to an out-of-memory condition Node.js SDK query , n1ql	20	4648	November 3, 2018

Setting Couchbase hostname to anything other then 127.0.0.1 causes "An unknown N1QL error occurred" in Node.js using n1ql query

Related topics