+++ This bug was initially created as a clone of Bug #1866490 +++

Description of problem:

When I set up the cluster logging instance (I've attached a yaml file for configuration), all pods start and run successfully.
Then after a few days, I encounter an error message when I open Kibana route:
"{"statusCode":500,"error":"Internal Server Error","message":"An internal server error occurred"}"

Version-Release number of selected component (if applicable):
Cluster Logging 4.5.0-202007012112

How reproducible:
A few days after setting up cluster logging instance

Steps to Reproduce:
1. Install Cluster Logging operator
2. Setting up Cluster Logging instance
3. After a few days, Kibana will throw Error 500

Actual results:
Kibana log:
  {"type":"error","@timestamp":"2020-07-29T15:00:27Z","tags":[],"pid":121,"level":"error","error":{"message":"Internal Server Error","name":"Error","stack":"Internal Server Error :: {\"path\":\"/.kibana/doc/config%3A6.8.1\",\"query\":{},\"statusCode\":500,\"response\":\"{\\\"code\\\":500,\\\"message\\\":\\\"Internal Error\\\",\\\"error\\\":{}}\\n\"}\n    at respond (/opt/app-root/src/node_modules/elasticsearch/src/lib/transport.js:308:15)\n    at checkRespForFailure (/opt/app-root/src/node_modules/elasticsearch/src/lib/transport.js:267:7)\n    at HttpConnector.<anonymous> (/opt/app-root/src/node_modules/elasticsearch/src/lib/connectors/http.js:166:7)\n    at IncomingMessage.wrapper (/opt/app-root/src/node_modules/elasticsearch/node_modules/lodash/lodash.js:4935:19)\n    at IncomingMessage.emit (events.js:203:15)\n    at endReadableNT (_stream_readable.js:1145:12)\n    at process._tickCallback (internal/process/next_tick.js:63:19)"},"url":{"protocol":null,"slashes":null,"auth":null,"host":null,"port":null,"hostname":null,"hash":null,"search":null,"query":{},"pathname":"/app/kibana","path":"/app/kibana","href":"/app/kibana"},"message":"Internal Server Error"}

Expected results:
Kibana page loading properly

Additional info:
I could successfully access through Google Chrome incognito mode, while the usual chrome browser still experienced error 500. It looks like authentication process is related.