# Can't enable system module: Compressor detection can only be called on some xcontent bytes or compressed xcontent bytes

**URL:** <https://discuss.elastic.co/t/cant-enable-system-module-compressor-detection-can-only-be-called-on-some-xcontent-bytes-or-compressed-xcontent-bytes/156971>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 16, 2018, 4:02am UTC](https://discuss.elastic.co/t/cant-enable-system-module-compressor-detection-can-only-be-called-on-some-xcontent-bytes-or-compressed-xcontent-bytes/156971 "2018-11-16T04:02:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![AlexJ](https://avatars.discourse-cdn.com/v4/letter/a/c89c15/32.png) [@AlexJ](https://discuss.elastic.co/u/AlexJ)\
**Post date:** [November 19, 2018, 12:12am UTC](https://discuss.elastic.co/t/cant-enable-system-module-compressor-detection-can-only-be-called-on-some-xcontent-bytes-or-compressed-xcontent-bytes/156971/3 "2018-11-19T00:12:39Z")

</div>

...yes! That is strange. This also seems to have fixed [my other issue](https://discuss.elastic.co/t/json-parse-exception-illegal-character-ctrl-char/156790/5) as well. Is compression known to be buggy?? It's not a major issue for us to leave it disabled.

---

_[View the full topic](https://discuss.elastic.co/t/cant-enable-system-module-compressor-detection-can-only-be-called-on-some-xcontent-bytes-or-compressed-xcontent-bytes/156971)._