May 11, 20242 yr Application Name: Meilisearch Application Website: https://www.meilisearch.com Docker Hub: https://hub.docker.com/r/getmeili/meilisearch GitHub: https://github.com/meilisearch/meilisearch Meilisearch is a RESTful search API. It aims to be a ready-to-go solution for everyone who wants a fast and relevant search experience for their end-users. Documentation: https://www.meilisearch.com/docs Support thread for Meilisearch docker image.
July 20, 20242 yr The default tag of getmeili/meilisearch:1.9.0 didn't work. I checked the docker registry and had to update it to getmeili/meilisearch:v1.9.0
July 20, 20242 yr Author On 7/20/2024 at 11:40 PM, duplexrat said: The default tag of getmeili/meilisearch:1.9.0 didn't work. I checked the docker registry and had to update it to getmeili/meilisearch:v1.9.0 Thanks. Fixed. Updated from :latest as there are frequent breaking changes that require manual migration. Edited September 2, 20241 yr by Collectathon
October 7, 20241 yr Hey! I'm trying to use meilisearch on Hoarder, but it doesn't work at all. docker logs meilisearch 888b d888 d8b 888 d8b 888 8888b d8888 Y8P 888 Y8P 888 88888b.d88888 888 888 888Y88888P888 .d88b. 888 888 888 .d8888b .d88b. 8888b. 888d888 .d8888b 88888b. 888 Y888P 888 d8P Y8b 888 888 888 88K d8P Y8b "88b 888P" d88P" 888 "88b 888 Y8P 888 88888888 888 888 888 "Y8888b. 88888888 .d888888 888 888 888 888 888 " 888 Y8b. 888 888 888 X88 Y8b. 888 888 888 Y88b. 888 888 888 888 "Y8888 888 888 888 88888P' "Y8888 "Y888888 888 "Y8888P 888 888 Config file path: "none" Database path: "./data.ms" Server listening on: "http://0.0.0.0:7700" Environment: "production" Commit SHA: "0df84bbba7db46680e83843dd6454257161a282f" Commit date: "2024-06-27T12:47:08Z" Package version: "1.9.0" Anonymous telemetry: "Disabled" Instance UID: "fc159891-e429-4f25-b308-529982a67d39" A master key has been set. Requests to Meilisearch won't be authorized unless you provide an authentication key. Check out Meilisearch Cloud! https://www.meilisearch.com/cloud?utm_campaign=oss&utm_source=engine&utm_medium=cli Documentation: https://www.meilisearch.com/docs Source code: https://github.com/meilisearch/meilisearch Discord: https://discord.meilisearch.com 2024-10-07T08:42:09.741320Z INFO actix_server::builder: starting 6 workers 2024-10-07T08:42:09.741349Z INFO actix_server::server: Actix runtime found; starting in Actix runtime No matter how i start the docker container (host, bridge, br0 without IP, br0 with IP), the listening IP won't change and it doesn't work in Hoarder. There is as good as NONE explaination given how to set up meilisearch/Hoarder (and Hoarder on unraid in general), you might consider providing a SHORT tutorial on this, cause without a tutorial it's a PAINFUL try & error leading to nothing.
October 7, 20241 yr Author 43 minutes ago, Gekko said: No matter how i start the docker container (host, bridge, br0 without IP, br0 with IP), the listening IP won't change and it doesn't work in Hoarder. There is as good as NONE explaination given how to set up meilisearch/Hoarder (and Hoarder on unraid in general), you might consider providing a SHORT tutorial on this, cause without a tutorial it's a PAINFUL try & error leading to nothing. I fail to see what further information needs to be provided outside of official documentation. The logs you show say that Meilisearch is starting fine and is working correctly. The server listening on will always say 0.0.0.0:7700. There are three variables for meilisearch Port - don't have to change it Appdata - wherever you app data is Master Key - whatever you want In Hoarder, you use two variables relating to Meilisearch. Master Key - same thing you setup before Address - this completely depends on which network you are using Hoarder. If you are using both in Host it should just be localhost:7700 or unraid_device_ip:7700 assuming you have changed any default values. If your in br0 then it will be the ip of the meilisearch docker container.
October 7, 20241 yr As i said, your descriptions are not sufficient to get this to work. To reconstruct my setup: meilisearch: br0 with manual IP 192.168.1.100 / port: 7700 hoarder: br0 with manual IP 192.168.1.101 / port: 3000 / linked with browserless fixed IP (192.168.1.99) on port 3000 / linked with meilisearch fixed IP (192.168.1.100) with port 7700 When entering search on hoarder's web gui, the search bar disappears and the text 'something went wrong' pops up. When entering the hoarder docker log, this error is all over: 2024-10-07T12:06:02.872Z error: [search][1455] search job failed: MeiliSearchApiError: The Authorization header is missing. It must use the bearer authorization method. MeiliSearchApiError: The Authorization header is missing. It must use the bearer authorization method. at /app/apps/workers/node_modules/.pnpm/[email protected]/node_modules/meilisearch/dist/bundles/meilisearch.cjs.js:378:19 at Generator.next (<anonymous>) at fulfilled (/app/apps/workers/node_modules/.pnpm/[email protected]/node_modules/meilisearch/dist/bundles/meilisearch.cjs.js:298:58) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
October 7, 20241 yr Author 8 hours ago, Gekko said: When entering the hoarder docker log, this error is all over: This is better. It indicates that you have not added http:// to the meilisearch address variable in the Hoarder template e.g. http://192.168.1.100:7700
October 21, 20241 yr Tried it on a different machine, problem is as i described above exactly the same: meilisearch does not work at all with Hoarder. Although all settings are made carefully, the search ends up with "something went wrong" without any further information. Logs are flooded with this error (i edited the IP adress): 2024-10-21T00:39:47.411671Z INFO HTTP request{method=GET host="xxx.xxx.xxx.xxx:7700" route=/indexes query_parameters= user_agent=node status_code=401 error=The Authorization header is missing. It must use the bearer authorization method.}: meilisearch: close time.busy=74.9µs time.idle=79.2µs 2024-10-21T00:39:49.438857Z WARN HTTP request{method=GET host="xxx.xxx.xxx.xxx:7700" route=/indexes query_parameters= user_agent=node status_code=401 error=The Authorization header is missing. It must use the bearer authorization method.}: tracing_actix_web::middleware: Error encountered while processing the incoming HTTP request: ResponseError { code: 401, message: "The Authorization header is missing. It must use the bearer authorization method.", error_code: "missing_authorization_header", error_type: "auth", error_link: "https://docs.meilisearch.com/errors#missing_authorization_header" } Edited October 21, 20241 yr by Gekko
October 21, 20241 yr Author I can't say that I have experienced this error, and I am unable to reproduce it. It is likely you would receive better support directly from the developer there. I have this same template and I know others are using it without issue as well. https://discord.gg/hJybMWE8Wd
October 21, 20241 yr I got it: I had the character ! in my meilisearch master key. That's it. Removed it and all works great.
October 21, 20241 yr Author 2 minutes ago, Gekko said: I got it: I had the character ! in my meilisearch master key. That's it. Removed it and all works great. That's frustrating. I'm glad it's working correctly now.
November 7, 20241 yr Question: I have Meilisearch working wih Hoarder, no problems. I now want to add another Docker container (Bar Assistant) that relies on Meilisearch. Can I just point it to the existing Meilisearch container as well? Or is it better to create another Meilisearch container? I know for some things (like Redis and Postgres) it is recommended to run multiple instances, but not sure whether that holds for Meilisearch. Thank you for supporting this template!
November 7, 20241 yr Author 4 hours ago, MrMastodonFarm said: Question: I have Meilisearch working wih Hoarder, no problems. I now want to add another Docker container (Bar Assistant) that relies on Meilisearch. Can I just point it to the existing Meilisearch container as well? Or is it better to create another Meilisearch container? I know for some things (like Redis and Postgres) it is recommended to run multiple instances, but not sure whether that holds for Meilisearch. Thank you for supporting this template! I actually run Bar Assistant on my server as well. It was such a pain to set up for use externally that I didn't share the template. As for Meilisearch, I use the same instance. I'm not sure which is preferred but I use a single instance.
December 19, 20241 yr I’m writing this to help anyone who might encounter the same error I faced while configuring Meilisearch. I was trying to deploy a Meilisearch container to work alongside Hoarder. However, Hoarder wouldn’t retrieve any search results. As someone mentioned earlier, it kept showing the error message: “Something went wrong.” When I checked Hoarder’s logs, I saw that it was a communication problem with the Meilisearch service. So, I went ahead and checked all the ports and IP addresses, but everything seemed correct. Next, I tried looking into the Meilisearch logs, but they wouldn’t open, which I thought was strange. The Docker dashboard showed that the container was running, so I was stuck trying to figure out what was wrong. I also noticed that every time I refreshed the page, the container status showed something like: “Restarted XX seconds ago.” This led me to check the advanced settings for Meilisearch, and that’s when I noticed an extra parameter for restarting the container unless it was manually stopped. Once I removed that parameter, I was finally able to access the logs. It turned out the issue was caused by an invalid master key. For anyone using the Unraid template, keep in mind that the version there appears to be outdated. The version in the GitHub repository is already at 1.1.3, which I successfully pulled and deployed without further issues. Cheers, everyone! Edited December 19, 20241 yr by gustolf
December 21, 20241 yr On 12/19/2024 at 3:54 AM, gustolf said: I’m writing this to help anyone who might encounter the same error I faced while configuring Meilisearch. I was trying to deploy a Meilisearch container to work alongside Hoarder. However, Hoarder wouldn’t retrieve any search results. As someone mentioned earlier, it kept showing the error message: “Something went wrong.” When I checked Hoarder’s logs, I saw that it was a communication problem with the Meilisearch service. So, I went ahead and checked all the ports and IP addresses, but everything seemed correct. Next, I tried looking into the Meilisearch logs, but they wouldn’t open, which I thought was strange. The Docker dashboard showed that the container was running, so I was stuck trying to figure out what was wrong. I also noticed that every time I refreshed the page, the container status showed something like: “Restarted XX seconds ago.” This led me to check the advanced settings for Meilisearch, and that’s when I noticed an extra parameter for restarting the container unless it was manually stopped. Once I removed that parameter, I was finally able to access the logs. It turned out the issue was caused by an invalid master key. For anyone using the Unraid template, keep in mind that the version there appears to be outdated. The version in the GitHub repository is already at 1.1.3, which I successfully pulled and deployed without further issues. Cheers, everyone! Thank you. Was having this issue several months ago and put it off to the side. Came back to it today and found this. Thank you for posting the fix.
December 21, 20241 yr Author On 12/19/2024 at 4:54 PM, gustolf said: For anyone using the Unraid template, keep in mind that the version there appears to be outdated. The version in the GitHub repository is already at 1.1.3, which I successfully pulled and deployed without further issues. The reason for this is that there are frequently breaking changes between version which require manual migration. You are welcome to update Meilisearch but the search functionality may break if you have data and don't perform this migration (or delete the database and regenerate). Due to this I would not recommend the :latest tag. As for the master key, it seems that it doesn't like symbols, I'll add this to the template.
January 8, 20251 yr When I navigate to http://192.168.0.111:7700 I get {"status":"Meilisearch is running"}. How can I access the mini dashboard?
January 8, 20251 yr Author 5 minutes ago, Christopher said: When I navigate to http://192.168.0.111:7700 I get {"status":"Meilisearch is running"}. How can I access the mini dashboard? mini-dashboard isn't in the Meilisearch package. It's a separate container you would have to run to visualise your data. Edited January 8, 20251 yr by Collectathon
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.