Running Splunk (in trial mode) behind a reverse proxy (wiki.splunk.com/Community:SplunkBehindAProxy) and have a problem with the DB Connect app not using the configured context root for selected actions.
In the DB Connect configuration in the web console, the URL associated with the 'Database Connections in Splunk Manager' button lacks the '/splunkv'/ context. A 'hover' over indicates the URL is '//myhost/manager/dbx/dbx/databases', an invalid context which displays a 404 error when clicked. Manually correcting the URL to include the 'splunkv' context ('//myhost/splunkv/manager/dbx/dbx/databases') displays the page correctly and allows interaction with the DB Connect configuration.
Is there a corresponding DB Connect proxy setting which corrects this error? Is there a general solution which ensures adherence to the root_endpoint value in web.conf?