Hi @graham.pople
thanks for your reply.
As I wrote, all required ports are accessible from the client side (verified via Telnet from client side) .
The strange thing is that the client tries to connect to the private IP of the Couchbase nodes (192…:11210) which is of course not publicly available. Instead it should connect to the public IP 134… as provided.
Could this issue relate to a misconfiguration of the Couchbase Server which seems to return the private IPs to the client instead of the public IPs to process the acutal operations ?
Regarding the bucket authentication: Thx for this hint, I also spotted this change in the recent updates but didn’t change it in my debugging code so far 