404 error for just /api calls. Nginx as proxy

data_smith · August 27, 2019, 1:54pm

I'm running Kibana 7.3 behind an Nginx proxy (in Kubernetes) and most things work but the /api calls don't seem to respect the basePath configuration. I set the basePath value and most calls prepend that and work, but all the /api calls don't prepend the basePath and therefore get 404 errors. Anyone else get this problem? Any solutions?

data_smith · August 27, 2019, 3:46pm

I worked around this issue by adding a location /api section that then adds the api:

location /api {
rewrite ^/api/(/.*)$ /api/$1 permanent;
}

The plugin should just prepend my basepath /mybasepath/api and then i wouldn't have had to do this.

mattkime · August 27, 2019, 9:37pm

Hope are you configuring the base path? The/api endpoint should 100% respect the basePath

data_smith · August 28, 2019, 1:08pm

Yea the basePath is definitely used because all of Kibana works except for the /api calls.

data_smith · August 28, 2019, 1:11pm

I don't see prepending basePath here:

github.com

elastic/kibana/blob/4025d1dfbb60a323c3a423fdb9e79674987dc906/src/legacy/core_plugins/console/public/src/kb.js

/*
 * Licensed to Elasticsearch B.V. under one or more contributor
 * license agreements. See the NOTICE file distributed with
 * this work for additional information regarding copyright
 * ownership. Elasticsearch B.V. licenses this file to you under
 * the Apache License, Version 2.0 (the "License"); you may
 * not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *    http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing,
 * software distributed under the License is distributed on an
 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
 */
import {
  TypeAutocompleteComponent,

This file has been truncated. show original

 $.ajax({
  url:
    '../api/console/api_server?sense_version=' +
    encodeURIComponent('@@SENSE_VERSION') +
    '&apis=' +
    encodeURIComponent(api),

dataType: 'json', // disable automatic guessing

mattkime · August 28, 2019, 2:46pm

Sorry, I meant to ask "How are you configuring the base path?" Typing is hard...

I should add that the bit of code you reference contains a relative url in order to support the base path.

data_smith · August 28, 2019, 3:15pm

This is running in Kubernetes using a nginx ingress controller proxy and I see the nginx.conf has /api location block for something else. But I don't understand why that would affect this case. If /mybasepath/api is then sent to Kibana /api it shouldn't matter that something else calls /api that goes to another application.

data_smith · August 28, 2019, 4:03pm

Does anyone know if the basepath is passed over in the header. What if the proxy somehow removes the basepath?

mattkime · September 1, 2019, 3:58am

Does anyone know if the basepath is passed over in the header. What if the proxy somehow removes the basepath?

The basepath is set via kibana.yml or arguments passed when the process is started - Configure Kibana | Kibana Guide [8.11] | Elastic

Can you connect to kibana without the proxy to see if you have the same problem?

data_smith · September 3, 2019, 12:47pm

Yes Kibana works without the proxy and it works with the proxy with the exception of the api calls. It only visibly affects things if I want to use the monitoring plugin otherwide for what I need it works. I do have the basePath set in kibana.yml by the way. No one else seems to run into this problem so maybe it's something weird with my setup with Kubernetes ingress controller.

system · October 1, 2019, 12:47pm

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.