# Uptime app 7.9.1 - "Internal server error"

**URL:** <https://discuss.elastic.co/t/uptime-app-7-9-1-internal-server-error/248384>\
**Category:** Synthetics\
**Created:** [September 11, 2020, 8:58pm UTC](https://discuss.elastic.co/t/uptime-app-7-9-1-internal-server-error/248384 "2020-09-11T20:58:56Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ManuelF](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@ManuelF](https://discuss.elastic.co/u/ManuelF)\
**Post date:** [September 15, 2020, 2:51pm UTC](https://discuss.elastic.co/t/uptime-app-7-9-1-internal-server-error/248384/6 "2020-09-15T14:51:26Z")

</div>

Hi @jkambic,

- Ran: `GET heartbeat-7.9.1/_mapping/field/observer.geo.name`

- Response:

- Stopped Heartbeat

- Removed index heartbeat-7.9.1

- Removed Legacy index template heartbeat-7.9.1

- Ran `GET /_cat/indices`. Found the other beats indexes, but nothing mentioning `heartbeat`

- Confirmed Uptime can't find any index to read from  

- Ran `.\heartbeat.exe setup` to create index and template (no errors)

- Started `heartbeat` service (no errors)

- Ran: `GET /_cat/indices`

- Response:

`green open heartbeat-7.9.1 iF4pc8ySSza5XtM_z40yzg 1 0 19 0 119.8kb 119.8kb`

- Confirmed index and index template added for `heartbeat-7.9.1`
- Ran: `GET heartbeat-7.9.1/_mapping/field/observer.geo.name`
- Response:  
{  
"heartbeat-7.9.1" : {  
"mappings" : { }  
}  
}

From this point the issue has been reproduced. `Uptime` is showing again the `"Internal server error"`. Is this Heartbeat version not mapping correctly when running the setup?

---

_[View the full topic](https://discuss.elastic.co/t/uptime-app-7-9-1-internal-server-error/248384)._