# Connection marked as failed because the onConnect callback failed: resource 'filebeat-7.5.1' exists, but it is not an alias"
**URL:** https://discuss.elastic.co/t/connection-marked-as-failed-because-the-onconnect-callback-failed-resource-filebeat-7-5-1-exists-but-it-is-not-an-alias/214253
**Category:** Beats
**Tags:** filebeat
**Created:** [January 8, 2020, 2:38pm UTC](https://discuss.elastic.co/t/connection-marked-as-failed-because-the-onconnect-callback-failed-resource-filebeat-7-5-1-exists-but-it-is-not-an-alias/214253 "2020-01-08T14:38:26Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Flaviu](https://discuss.elastic.co/u/Flaviu)
#### Post date: [January 8, 2020, 2:38pm UTC](https://discuss.elastic.co/t/connection-marked-as-failed-because-the-onconnect-callback-failed-resource-filebeat-7-5-1-exists-but-it-is-not-an-alias/214253/1 "2020-01-08T14:38:26Z")
Hello,
I have just installed a new server with filebeat 7.5.1 and for some reason, after I restart the filebeat or the server I get this error:
```
Connection marked as failed because the onConnect callback failed:
resource 'filebeat-7.5.1' exists, but it is not an alias"
```
if I go in kibana and delete the "filebeat-7.5.1" index I start to see logs coming in in the kibana/elasticsearch server, and the above error disappears from the filebeat error logs.
If I restart the filebeat process or the server altogether the above error starts to appear again and the logs are not pus anymore in kibana/elasticsearch. Te repair this I just need to go back to kibana and delete the index.
I have some more servers with a different version of filebeat and I don't have this issue.
Am I doing something wrong?
Thank you,
---
### Author:  [@faec](https://discuss.elastic.co/u/faec)
#### Post date: [January 9, 2020, 8:33pm UTC](https://discuss.elastic.co/t/connection-marked-as-failed-because-the-onconnect-callback-failed-resource-filebeat-7-5-1-exists-but-it-is-not-an-alias/214253/2 "2020-01-09T20:33:07Z")
Could you share your filebeat configuration? You can preserve the formatting by putting triple backticks (```) on the lines before and after the config. It looks like your problems are related to ILM (see [here](https://www.elastic.co/guide/en/beats/filebeat/current/ilm.html)), but I'd need to see the configuration to say more. Are you possibly using more than one filebeat with the same elasticsearch server? If so, they might have conflicting index settings.
---
### Author:  [@TCBeeekley](https://discuss.elastic.co/u/TCBeeekley)
#### Post date: [January 16, 2020, 5:26pm UTC](https://discuss.elastic.co/t/connection-marked-as-failed-because-the-onconnect-callback-failed-resource-filebeat-7-5-1-exists-but-it-is-not-an-alias/214253/3 "2020-01-16T17:26:06Z")
I'm having this same issue, running Filebeat to ship logs from k8s (AWS EKS) to Elastic Cloud.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 13, 2020, 5:26pm UTC](https://discuss.elastic.co/t/connection-marked-as-failed-because-the-onconnect-callback-failed-resource-filebeat-7-5-1-exists-but-it-is-not-an-alias/214253/4 "2020-02-13T17:26:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.