# Filebeat local date wrong
**URL:** https://discuss.elastic.co/t/filebeat-local-date-wrong/95100
**Category:** Beats
**Tags:** filebeat
**Created:** [July 31, 2017, 1:14am UTC](https://discuss.elastic.co/t/filebeat-local-date-wrong/95100 "2017-07-31T01:14:39Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Puk](https://discuss.elastic.co/u/Puk)
#### Post date: [July 31, 2017, 1:14am UTC](https://discuss.elastic.co/t/filebeat-local-date-wrong/95100/1 "2017-07-31T01:14:39Z")
Total newbie here trying to get ELK Stack working in a test environment first ahead of deploying. I've managed to get everything working fine, including Winlogbeat and metricbeat, but filebeat for my linux hosts is giving me issues.
I have it shipping logs (messages and secure) fine, but when I search them in Kibana the date is wrong in the region of -14hrs.
When I run filebeat -e -v "publish" I can see the timestamp there is incorrect so thats where it is going wrong but I don't know how to change it. My server timestamp itself is correct and the time/date is correct in the message section of the log, but the @timestamp is not.
Any ideas?
---
### Author:  [@Puk](https://discuss.elastic.co/u/Puk)
#### Post date: [July 31, 2017, 3:25am UTC](https://discuss.elastic.co/t/filebeat-local-date-wrong/95100/2 "2017-07-31T03:25:55Z")
Fixed it. Removed the filebeat client and re-installed from the same RPM and its working fine now with the correct date. No idea why it went wrong the first time as nothing has changed.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 28, 2017, 3:26am UTC](https://discuss.elastic.co/t/filebeat-local-date-wrong/95100/3 "2017-08-28T03:26:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.