Kibana doesn't see the indices

Hi there. I've been experiencing a problem with Kibana - the indices don't show in index patterns menu even though all the indexes are present in index management menu.

The whole thing runs under proxy.
Request: http://192.168.10.6:5601/elasticsearch/*/_search?ignore_unavailable=true
Response:
proxy_response:
{ "took": 833, "timed_out": false, "_shards": { "total": 4, "successful": 4, "skipped": 0, "failed": 0 }, "hits": { "total": { "value": 10000, "relation": "gte" }, "max_score": null, "hits": [] }, "aggregations": { "indices": { "doc_count_error_upper_bound": 0, "sum_other_doc_count": 0, "buckets": [ { "key": "logs-64cb0a97d4594f79bf2b2a5bfd9763e1-2019-08-01", "doc_count": 185111 }, { "key": ".monitoring-es-7-2019.08.01", "doc_count": 201 }, { "key": ".monitoring-kibana-7-2019.08.01", "doc_count": 24 }, { "key": ".kibana", "doc_count": 2 } ] } } }

kibana.yml:
server.port: 5601
server.host: 192.168.10.6
server.basePath: /dashboard/monitoring/logs_proxy
server.rewriteBasePath: false
elasticsearch.hosts: ["http://192.168.10.6:9200"]
elasticsearch.preserveHost: True
kibana.index: ".kibana"
kibana.defaultAppId: "discover"
elasticsearch.shardTimeout: 0
elasticsearch.startupTimeout: 5000

logging.silent: false
logging.quiet: false
logging.verbose: true
optimize.useBundleCache: False

xpack.monitoring.enabled: true
xpack.monitoring.kibana.collection.enabled: true
xpack.monitoring.ui.enabled: true

Index patterns menu:


Index management menu:

elasticsearch.yml:
cluster.name: monasca_elastic
node.name: "devstack"
node.master: true
node.data: true
path.data: /opt/stack/data/elasticsearch
path.logs: /opt/stack/logs/elasticsearch
network.bind_host: 192.168.10.6
network.publish_host: 192.168.10.6
transport.tcp.port: 9300
http.port: 9200
cluster.initial_master_nodes: ["192.168.10.6"]
xpack.security.enabled: false
xpack.monitoring.enabled: true
xpack.monitoring.collection.enabled: true
xpack.monitoring.elasticsearch.collection.enabled: true

Do you see the same problem if you bypass the proxy?

without proxy
request:
curl http://192.168.10.6:5601/elasticsearch/%2A/_search?ignore_unavailable=true -d'{"size":0,"aggs":{"indices":{"terms":{"field":"_index","size":200}}}}' -H 'kbn-xsrf: reporting'
response:
{"statusCode":500,"error":"Internal Server Error","message":"An internal server error occurred"}

Elasticseach and Kibana - both 7.2.1

Can you bypass the proxy and access Kibana? How is the proxy set up?

if I set rewriteBasePath to true, everything's accessible outside proxy and I can see all of my indices.
Otherwise it's not accesible - I'm getting such errors:
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'nonce-WlAeJVZ1TIIKfZ8U'". Either the 'unsafe-inline' keyword, a hash ('sha256-SHHSeLc0bp6xt4BoVVyUy+3IbVqp3ujLaR+s+kSP5UI='), or a nonce ('nonce-...') is required to enable inline execution. bootstrap.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
Proxy is basically rewriting the link, removing basePath, packing headers and sending a request via Python urllib.request.Request.

btw, in 7.3.0(both es and kibana) error looks like that:
Uncaught (in promise) Error: Loading chunk 169 failed. (missing: http://192.168.10.6/dashboard/monitoring/logs_proxy/built_assets/dlls/icon.logo_elasticsearch-js.bundle.dll.js) at requireEnsure (/dashboard/monitoring/logs_proxy/built_assets/dlls/vendors.bundle.dll.js:1) at Array.map (<anonymous>) at webpackAsyncContext (/dashboard/monitoring/logs_proxy/built_assets/dlls/vendors.bundle.dll.js:192) at EuiIcon.loadIconComponent (/dashboard/monitoring/logs_proxy/built_assets/dlls/vendors.bundle.dll.js:54) at new EuiIcon (/dashboard/monitoring/logs_proxy/built_assets/dlls/vendors.bundle.dll.js:54) at vf (/dashboard/monitoring/logs_proxy/built_assets/dlls/vendors.bundle.dll.js:224) at Og (/dashboard/monitoring/logs_proxy/built_assets/dlls/vendors.bundle.dll.js:224) at Tg (/dashboard/monitoring/logs_proxy/built_assets/dlls/vendors.bundle.dll.js:224) at bi (/dashboard/monitoring/logs_proxy/built_assets/dlls/vendors.bundle.dll.js:224) at ci (/dashboard/monitoring/logs_proxy/built_assets/dlls/vendors.bundle.dll.js:224)

If it ever helps anyone, the issue was resolved by adding Content-Type": "application/json" to the headers of the request. Good luck everyone!