)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at handler (/usr/share/kibana/src/core/server/http/router/router.js:124:50)
at module.exports.internals.Manager.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/toolkit.js:45:28)
at Object.internals.handler (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:46:20)
at exports.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:31:20)
at Request._lifecycle (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:312:32)
at Request._execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:221:9)"},"url":"https://kb.contoso.com/api/fleet/setup","message":"Internal Server Error"}
{"type":"response","@timestamp":"2021-02-17T07:34:58-08:00","tags":["access:fleet-read"],"pid":806,"method":"post","statusCode":500,"req":{"url":"/api/fleet/setup","method":"post","headers":{"host":"kb.contoso.com","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Firefox/85.0","accept":"*/*","accept-language":"en-US,en;q=0.5","accept-encoding":"gzip, deflate, br","referer":"https://kb.contoso.com/s/space-name/app/fleet","content-type":"application/json","kbn-version":"7.11.0","origin":"https://kb.contoso.com","connection":"keep-alive","content-length":"0"},"remoteAddress":"192.168.1.100","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Firefox/85.0","referer":"https://kb.contoso.com/s/space-name/app/fleet"},"res":{"statusCode":500,"responseTime":40519,"contentLength":9},"message":"POST /api/fleet/setup 500 40519ms - 9.0B"}
```
---
### Author:  [@rashmi](https://discuss.elastic.co/u/rashmi)
#### Post date: [February 17, 2021, 3:58pm UTC](https://discuss.elastic.co/t/everything-is-broken-after-upgrade-to-7-11/263973/9 "2021-02-17T15:58:14Z")
I think you are hitting this issue [[Fleet] Upgrade to 7.11 failed · Issue #90984 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/90984) . It will be shipped with 7.11.1
Thanks
Rashmi
---
### Author:  [@MakoWish](https://discuss.elastic.co/u/MakoWish)
#### Post date: [February 17, 2021, 4:00pm UTC](https://discuss.elastic.co/t/everything-is-broken-after-upgrade-to-7-11/263973/10 "2021-02-17T16:00:13Z")
It is the same issue, but the workaround that seems to be working for others did not work for me.
---
### Author:  [@skh](https://discuss.elastic.co/u/skh)
#### Post date: [February 17, 2021, 4:16pm UTC](https://discuss.elastic.co/t/everything-is-broken-after-upgrade-to-7-11/263973/11 "2021-02-17T16:16:47Z")
@MakoWish I think you might be seeing the same problem as described in [Unable to initialize Fleet - An internal server error occurred](https://discuss.elastic.co/t/unable-to-initialize-fleet-an-internal-server-error-occurred/264368)
We're tracking this in [[Fleet] [Security Solution] Fleet cannot upgrade: Transform stop times out · Issue #91570 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/91570)
---
### Author:  [@PublicName](https://discuss.elastic.co/u/PublicName)
#### Post date: [February 17, 2021, 8:20pm UTC](https://discuss.elastic.co/t/everything-is-broken-after-upgrade-to-7-11/263973/12 "2021-02-17T20:20:47Z")
7.11.1 did not resolve the issue.
It made matters worse not sure if @MakoWish has had any luck but I for one ran into his issue with 7.11. 7.11.1 has another error where it will not connect to Elastic at all when it is clearly running and accepting connections.
---
### Author:  [@MakoWish](https://discuss.elastic.co/u/MakoWish)
#### Post date: [February 17, 2021, 9:37pm UTC](https://discuss.elastic.co/t/everything-is-broken-after-upgrade-to-7-11/263973/13 "2021-02-17T21:37:53Z")
7.11.1 also did not fix the issue for me. I am still receiving the same error.
```auto
Unable to initialize Fleet
An internal server error occurred.
```
---
### Author:  [@searchtool](https://discuss.elastic.co/u/searchtool)
#### Post date: [February 17, 2021, 9:38pm UTC](https://discuss.elastic.co/t/everything-is-broken-after-upgrade-to-7-11/263973/14 "2021-02-17T21:38:56Z")
> [@skh](#):
>
> @MakoWish I think you might be seeing the same problem as described in [Unable to initialize Fleet - An internal server error occurred](https://discuss.elastic.co/t/unable-to-initialize-fleet-an-internal-server-error-occurred/264368)
>
> We're tracking this in [[Fleet] [Security Solution] Fleet cannot upgrade: Transform stop times out · Issue #91570 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/91570)
Adding the transform node solved my issue!
---
### Author:  [@MakoWish](https://discuss.elastic.co/u/MakoWish)
#### Post date: [February 18, 2021, 4:17pm UTC](https://discuss.elastic.co/t/everything-is-broken-after-upgrade-to-7-11/263973/15 "2021-02-18T16:17:44Z")
I just saw that this morning and came here to link to the post, but you beat me to it! 🙂 Adding the Transform role solved the issue for me as well.
Slightly off-topic, but question on the role... I enabled it on both our Kibana servers for now (ES coordinating nodes), but what node does "best practice" say to enable it on?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 18, 2021, 4:17pm UTC](https://discuss.elastic.co/t/everything-is-broken-after-upgrade-to-7-11/263973/16 "2021-03-18T16:17:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.