Thanks for your responses!
The Data service is configured and is working correctly. Here's how I know:
- I can connect to Couchbase using the same .NET Core DLL on a different machine (Windows) and execute all operations against the database successfully (verified documents are created, deleted, etc in the Couchbase console).
- I can connect to Couchbase on the same machine (Linux CentOS) using Node.js and execute all operations successfully.
- The Couchbase Console lists Data, Index, and Query as services enabled on the server node.
The problem seems to be specifically related to the CouchbaseNetClient on Linux.
I did change the server connection to the suggested format
http://myserver:8091, but I receive the same error. I even tried 'http://myserver:8091/pools', 'http://myserver:8091/pools/default', 'http://myserver:8091/pools/default/mybucket' and a bunch of other variations to no effect.
Also, when I
curl 'http://myserver:8091/pools/default', it showed
"couchApiBase":"http://myserver:8092/","couchApiBaseHTTPS":"https://myserver:18092/". The ports are different, so I tried these and they don't work either - same error.
I also set the
UseSsl configuration to
true and changed the connection to
https. I logged into the Couchbase Console and downloaded the self-signed certificate and added it as a trusted certificate on Linux as well. I still receive the same error.
I guess the CouchbaseNetClient is not getting the correct metadata from the server to know that the cluster has the Data service enabled???
I'm at a loss of where to go from here. Any ideas of something else I can try? Has anyone been able to replicate the issue on Linux?