Closed cjconnor24 closed 3 months ago
Hi @cjconnor24 - this repository is specifically for hosting our Dockerfiles, and isn't generally monitored for support requests. So I'll close this ticket.
For what it's worth, I've reproduced your symptom. I found an older ticket which suggests this may have worked in the past, but it was from quite some time ago. Evidently something has broken it in the meantime. I will ask around internally to see if this is something we should support, and if so, I'll create a new ticket and update you here. In the meantime, however, I'm afraid this isn't going to work except at the root of a domain. You might consider using something like Traefik in your Docker deployments to enable hostname-based traffic redirection; we use it for a number of similar setups here.
Cheers @ceejatec appreciate was a fine line between issue / support :) thanks for the help
Description: We are running Couchbase on Docker in our developer environments and would like to move the Couchbase UI behind our reverse proxy for better accessibility.
Current Access: Direct access: http://server.devdomain.com:8091/
Desired Access: Through reverse proxy: https://server.devdomain.com/db/
Problem: After configuring the reverse proxy, the Couchbase login page gets returned correctly.
However, some parts of the UI try to re-route to the root domain, causing issues with loading JavaScript files and other resources.
Question: How can we set a base URL for Couchbase, perhaps via an environment variable or configuration property, so that all links and resources resolve correctly to the
/db
base path?