Thx for the compliment and quick reply @ingenthr!
I’ll give the new SDK a shot.
I setup the docker container exactly as that article suggested but to clarify, the cloud provider’s web app service only exposes port 80 and 443. Internally as part of their system, I’m able to set the environment variable PORT to 8091. With that variable set, I can successfully access the server with just the base url. Appending the port to the end of that url fails with a timeout. If possible, I’d like to force the SDK to use the base url without attaching a port at all. Is that possible?
The reason why I think it’s adding port 8091 is because while troubleshooting, I set the URL to a fake address http://servername.cloud.com to see what would happen, and it threw the exception: “Couchbase.Utils.UnsupportedAddressFamilyException: http://servername.cloud.com:8091/pools”. Based on that exception, it seems like the SDK added :8091/pools to the end of the URL.
Now, if I use my real url in the SDK, I get a timeout exception which is exactly what happens if I append the port to the end of the base url via a web browser. If I then remove that port via the web browser, success.
I hope that further claries the issue.