Closed xucito closed 5 years ago
Pinging @elastic/kibana-operations
To add to this issue, it seems accessing the identical cluster via a public IP does not cause this issue, it only happens if I use the local ip address from another machine within the same network (i.e. VPN'd device).
I'm seeing similar since updating from a 6.4.x to 6.5.4 yesterday on an AWS hosted Elasticsearch.
Page loads OK in browser, basic searches work, but then (maybe 30 seconds after initial page load?). Page resets with Kibana did not load properly. Check the server output for more information.
big red error message. Chrome then shows ERR_CONNECTION_RESET
messages in the console for static assets such as kibana.style.css
, manifest.json
,...
(Note we have our own proxy in front that signs the AWS requests with AWS credentials, and right now I'm kubectl port-forwarding to get there, so a few extra potential culprits in the serving path - but this previously worked fine prior to the update)
@xucito @aeijdenberg could either of you provide copies of the assets that are regularly getting blocked, and any proxy configuration you can share? I'm 99% sure this happening at the proxy layer and not in Kibana, but maybe we can help figure out what change between 6.4 and 6.5/6.6 could have triggered the new behavior.
@spalger - sadly for this bug, I'm no longer able to reproduce. This occurred for a few hours yesterday quite consistently, and then stopped. I wonder if maybe something was cached somewhere that has now cleared?
Thank you for the follow-up - if we see this re-occur I'll update this issue.
In that case I'll close the issue for now, if either of you can reproduce later feel free to reopen here.
Kibana version: docker.elastic.co/kibana/kibana:6.6.1 Elasticsearch version: docker.elastic.co/elasticsearch/elasticsearch:6.6.1 Server OS version: Centos 7.4 Browser version: Google Chrome Version 72.0.3626.121 (Official Build) (64-bit) Browser OS version: Windows 10 Original install method (e.g. download page, yum, from source, etc.): Docker Describe the bug: When accessing Kibana, css files are reporting ERR_CONNECTION_RESET Steps to reproduce:
Expected behavior:
Screenshots (if relevant): Error I receive
Errors in browser console (if relevant):
Example:
Provide logs and/or server output (if relevant): Nothing suspicious in logs.
Any additional context: