You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to nextcloud ( 1 week old) and been battling with getting elastic search working with full text search for the last 4 days. I was often getting errors in the terminal of " username must be a string " or words to that effect , and similar errors like
An unhandled exception has been thrown:
TypeError: array_key_exists(): Argument #2 ($array) must be of type array, false given in /var/www/html/apps/fulltextsearch_elasticsearch/lib/Platform/ElasticSearchPlatform.php
Anyway, what i noticed and how i got around it was ... my password has a # on the end of it , so 123456# for example.
in the UI, i was making the address of servlet : http://larry:123456#@localhost:9200 This was the root of the problem. In the end i had to make it URL encoded http://larry:123456%23@localhost:9200 as it appears not to like having a # in the password field.
More so a tip for others in the future than a bug report as such, but worth taking note of i guess shrug i'm not a guru so this may be common knowledge, but i spent way to long discovering that and wanted to document it :)
The text was updated successfully, but these errors were encountered:
I'm new to nextcloud ( 1 week old) and been battling with getting elastic search working with full text search for the last 4 days. I was often getting errors in the terminal of " username must be a string " or words to that effect , and similar errors like
Anyway, what i noticed and how i got around it was ... my password has a # on the end of it , so 123456# for example.
in the UI, i was making the address of servlet :
http://larry:123456#@localhost:9200
This was the root of the problem. In the end i had to make it URL encodedhttp://larry:123456%23@localhost:9200
as it appears not to like having a # in the password field.More so a tip for others in the future than a bug report as such, but worth taking note of i guess shrug i'm not a guru so this may be common knowledge, but i spent way to long discovering that and wanted to document it :)
The text was updated successfully, but these errors were encountered: