Internal Server Error After Update

Hello, I updated to 7.6.2 today, and am now greeted with the following error:

    Version: 7.6.2
    Build: 29199
    Error: Internal Server Error
    at fetchResponse$ (http://fluent.dev.brandcoders.com/bundles/commons.bundle.js:3:3009775)
    at s (http://fluent.dev.brandcoders.com/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:338:774550)
    at Generator._invoke (http://fluent.dev.brandcoders.com/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:338:774303)
    at Generator.forEach.e.<computed> [as next] (http://fluent.dev.brandcoders.com/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:338:774907)
    at s (http://fluent.dev.brandcoders.com/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:338:774550)
    at t (http://fluent.dev.brandcoders.com/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:338:775045)
    at http://fluent.dev.brandcoders.com/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:338:775195

I did some searching and found this github issue. My situation is basically the same, I am behind an apache proxy, but my ProxyPath is just for /, not each route individually.

Apache Config

    <VirtualHost _default_:443>
    SSLProxyEngine on
    SSLProxyVerify none
    SSLProxyCheckPeerCN off
    SSLProxyCheckPeerName off
    SSLProxyCheckPeerExpire off
    #SSLEngine On
    ProxyPass / https://localhost:5601/ connectiontimeout=900 timeout=900
    ProxyPassReverse / https://localhost:5601/
    SetEnv force-proxy-request-1.0 1
    SetEnv proxy-nokeepalive 1

Kibana Config (yes, basePath is commented out, which means it should default to /app/kibana, right?)

    server.host: "0.0.0.0"
    #server.basePath: ""
    #server.rewriteBasePath: false

Looks like you're getting an Internal Server Error. Do you have the logs from the Kibana instances available?

Hello, thank you for the reply, the most recent things in the log file are just the traffic trying to access kibana, but no 500 errors. And the service seems to be up and running just fine.

Do you have a way for me to attach my log files, or paste something larger than the character limit?

Hi Tyler, just checking to see if you have either 1) a way for me to get you my log file, since I don't see a way to attach a file to a post, and its way over the character limit, or 2) any ideas or official documentation about the correct way to use an apache proxy in front of kibana, since the kibana and elasticsearch services seem to be running fine on the server, and there are no errors in either of their respective logs, or the apache logs for that matter.

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