# Filtering by non-latin characters

**URL:** <https://discourse.getcockpit.com/t/filtering-by-non-latin-characters/2712>\
**Category:** Support\
**Created:** [February 20, 2023, 6:49pm UTC](https://discourse.getcockpit.com/t/filtering-by-non-latin-characters/2712 "2023-02-20T18:49:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sock4proxy](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/sock4proxy/32/1146_2.png) [@sock4proxy](https://discourse.getcockpit.com/u/sock4proxy)\
**Post date:** [February 20, 2023, 6:49pm UTC](https://discourse.getcockpit.com/t/filtering-by-non-latin-characters/2712/1 "2023-02-20T18:49:52Z")

</div>

Hello  
When I try to search for text containing non-Latin characters I get the error `DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range.` in the browser console.  
When trying to filter by a word from Latin letters, everything works correctly.  
Is there a way to make the filter work?

---

<div class="post-metadata">

**Author:** ![artur](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/artur/32/4_2.png) [@artur](https://discourse.getcockpit.com/u/artur)\
**Post date:** [February 22, 2023, 12:02am UTC](https://discourse.getcockpit.com/t/filtering-by-non-latin-characters/2712/2 "2023-02-22T00:02:13Z")

</div>

Thanks for reporting. This is already fixed in the latest dev codebase. You can download it [here](https://files.getcockpit.com/?dir=releases/develop)

---

<div class="post-metadata">

**Author:** ![sock4proxy](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/sock4proxy/32/1146_2.png) [@sock4proxy](https://discourse.getcockpit.com/u/sock4proxy)\
**Post date:** [February 23, 2023, 12:19am UTC](https://discourse.getcockpit.com/t/filtering-by-non-latin-characters/2712/3 "2023-02-23T00:19:01Z")

</div>

Unfortunately, I cannot provide access to the project where the described problem occurs, it is not in the public domain. If you have something like a demo site with deployed cms I can try to reproduce the bug there and describe the steps needed to reproduce it.

edit:  
it was answer to your previous version of answer, about providing an example  
in production i am using 2.3.9-1677111728 version, and bug still reproduced  
later I will try to reproduce the error on the version from the link and report the result  
thanks for the quick response

---

<div class="post-metadata">

**Author:** ![artur](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/artur/32/4_2.png) [@artur](https://discourse.getcockpit.com/u/artur)\
**Post date:** [February 23, 2023, 12:34am UTC](https://discourse.getcockpit.com/t/filtering-by-non-latin-characters/2712/4 "2023-02-23T00:34:00Z")

</div>

Please get the latest codebase from the shared link above. After updating your instance, also try to clear the browser cache to make sure not to load any cached assets.

If it still appears, can you please share an example string you use in your search?

Thanks!

---

<div class="post-metadata">

**Author:** ![sergefy13](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/sergefy13/32/1432_2.png) [@sergefy13](https://discourse.getcockpit.com/u/sergefy13)\
**Post date:** [March 12, 2024, 9:01am UTC](https://discourse.getcockpit.com/t/filtering-by-non-latin-characters/2712/5 "2024-03-12T09:01:41Z")

</div>

Hey! What should I replace in directory not to loose my data? Isn’t there any auto-updater?