# Encoding problem after upgrade to Elastic 2.3

**URL:** <https://discuss.elastic.co/t/encoding-problem-after-upgrade-to-elastic-2-3/46828>\
**Category:** Elasticsearch\
**Created:** [April 8, 2016, 4:06pm UTC](https://discuss.elastic.co/t/encoding-problem-after-upgrade-to-elastic-2-3/46828 "2016-04-08T16:06:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![TDV](https://avatars.discourse-cdn.com/v4/letter/t/f475e1/32.png) [@TDV](https://discuss.elastic.co/u/TDV)\
**Post date:** [April 8, 2016, 4:06pm UTC](https://discuss.elastic.co/t/encoding-problem-after-upgrade-to-elastic-2-3/46828/1 "2016-04-08T16:06:22Z")

</div>

Hi  
We faced encoding problem after upgrading Elastic from 2.1.1 to 2.3.0 and logstash from 2.1.1 to 2.3.0

Elastic server configuration:

Elastic 2.3.0  
Logstash 2.3.0  
Java 8 update 77  
Windows server 2012 R2

We use Logstash for log parsing and loading them in Elastic.  
There are cyrillic symbols in logs and they turned into questions ????? (in Elastic) after upgrade.  
Logs encoding is Cyrrilic Windows 1251 (CP1251)

Were there some changes in encoding settings in Elastic/Logstash (in 2.3.0 releases)?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 9, 2016, 7:08am UTC](https://discuss.elastic.co/t/encoding-problem-after-upgrade-to-elastic-2-3/46828/2 "2016-04-09T07:08:26Z")

</div>

I'm not aware of problems, but try LS 2.3.1 as 2.3.0 had some issues.

---

<div class="post-metadata">

**Author:** ![TDV](https://avatars.discourse-cdn.com/v4/letter/t/f475e1/32.png) [@TDV](https://discuss.elastic.co/u/TDV)\
**Post date:** [April 11, 2016, 1:17pm UTC](https://discuss.elastic.co/t/encoding-problem-after-upgrade-to-elastic-2-3/46828/3 "2016-04-11T13:17:29Z")

</div>

Upgrade to LS 2.3.1 helped

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:00pm UTC](https://discuss.elastic.co/t/encoding-problem-after-upgrade-to-elastic-2-3/46828/4 "2017-07-05T23:00:43Z")

</div>