I have set up the LLM, embedding, and persona features; however, my prompt is not providing the expected responses from the questions and answers or the available wiki resources within our community. Self-Hosted LLM: mistral:latest Self-Hosted Embedding: all-minilm:latest Persona: [image] [image] [image] Could anyone help me further with what needs to be done?

[imagen] viswanatha: Self-Hosted LLM: mistral:latest What exact Mistral model is this? [imagen] viswanatha: however, my prompt is not providing the expected responses Can you share the prompt? [imagen] viswanatha: [image] You can add Search as a “Forced Tool” for the first interaction to help ground the model.

@Falco, The below are the details for tailing reply: What exact Mistral model is this? LLM Model : mistral:latest Link: The model at https://ollama.com/library/mistral:latest is: Mistral 7B v0.3 — a 7 billion parameter open-source model released by Mistral AI. Can you share the prompt? System prompt: You are a community knowledge assistant designed for this forum called {site_title} and with site URL {site_url}, having engineers as users. Always search and reference relevant forum posts, wiki articles, and tagged discussions before generating an answer. Your first priority is to use retrieved forum content (via embeddings search) to craft responses. Prefer summaries and citations from existing posts. If multiple related topics are found, combine them clearly. Only if no relevant content exists, respond using your general knowledge through the LLM. Include topic titles or URLs when referencing posts. Never hallucinate or invent answers not supported by forum data. Be factual, concise, and professional. When users ask broad questions, prefer summarizing multiple sources rather than guessing. Always prefer context from categories, tags, and wikis indexed in embeddings. Updated the forced Tool as suggested

[imagen] viswanatha: Mistral 7B v0.3 — a 7 billion parameter open-source model released by Mistral AI. I’m afraid a rehashed 2023 model won’t make the cut here. Also, from Ollama own documentation for this model, it only supports tool calling on the raw API, which is not what we use. Overall, this is a poor choice for AI Bot today. Instead, use one of the following [imagen] qwen3-vl:8b The most powerful vision-language model in the Qwen model family to date. [imagen] gemma3:12b The current, most capable model that runs on a single GPU. [imagen] deepseek-r1:8b DeepSeek-R1 is a family of open reasoning models with performance approaching that of leading models, such as O3 and Gemini 2.5 Pro.

Hi @Falco, and afraid, thank you for the Inputs. We will check and update you further.

@Falco Facing 502 error while enabling LLM. Please find the Logs below [image] [image] Message Unicorn worker received USR2 signal indicating it is about to timeout, dumping backtrace for main thread config/unicorn.conf.rb:203:in `backtrace' config/unicorn.conf.rb:203:in `block (2 levels) in reload' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:229:in `wait_readable' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:229:in `rbuf_fill' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:199:in `readuntil' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:209:in `readline' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http/response.rb:158:in `read_status_line' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http/response.rb:147:in `read_new' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:2420:in `block in transport_request' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:2411:in `catch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:2411:in `transport_request' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:2384:in `request' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/net_patches.rb:19:in `block in request_with_mini_profiler' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/mini_profiler/profiling_methods.rb:45:in `step' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/net_patches.rb:18:in `request_with_mini_profiler' /var/www/discourse/plugins/discourse-ai/lib/completions/endpoints/base.rb:168:in `block in perform_completion!' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:1632:in `start' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:1070:in `start' /var/www/di... Backtrace /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:130:in `block in warn' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:231:in `block in dispatch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:231:in `each' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:231:in `dispatch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:130:in `warn' /var/www/discourse/lib/signal_trap_logger.rb:40:in `public_send' /var/www/discourse/lib/signal_trap_logger.rb:40:in `block (2 levels) in ensure_logging_thread_running' :187:in `loop' /var/www/discourse/lib/signal_trap_logger.rb:37:in `block in ensure_logging_thread_running'

Set provider as OpenAI if you are using the OpenAI compatible API of Ollama.

@Falco I have tired with openAI provider still issue is persists. Message Unicorn worker received USR2 signal indicating it is about to timeout, dumping backtrace for main thread config/unicorn.conf.rb:203:in `backtrace' config/unicorn.conf.rb:203:in `block (2 levels) in reload' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:229:in `wait_readable' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:229:in `rbuf_fill' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:199:in `readuntil' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:209:in `readline' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http/response.rb:158:in `read_status_line' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http/response.rb:147:in `read_new' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:2420:in `block in transport_request' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:2411:in `catch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:2411:in `transport_request' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:2384:in `request' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/net_patches.rb:19:in `block in request_with_mini_profiler' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/mini_profiler/profiling_methods.rb:45:in `step' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/net_patches.rb:18:in `request_with_mini_profiler' /var/www/discourse/plugins/discourse-ai/lib/completions/endpoints/base.rb:168:in `block in perform_completion!' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:1632:in `start' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:1070:in `start' /var/www/di... Backtrace /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:130:in `block in warn' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:231:in `block in dispatch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:231:in `each' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:231:in `dispatch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/broadcast_logger.rb:130:in `warn' /var/www/discourse/lib/signal_trap_logger.rb:40:in `public_send' /var/www/discourse/lib/signal_trap_logger.rb:40:in `block (2 levels) in ensure_logging_thread_running' :187:in `loop' /var/www/discourse/lib/signal_trap_logger.rb:37:in `block in ensure_logging_thread_running'

Can your Discourse container access the service in the port 11434? If it’s running on the host you need to provide a way for the network cross the container boundary.

Yes, I was able access one of the LLM model ealier with same port with Discourse container

[imagen] Falco: Can your Discourse container access the service in the port 11434? If it’s running on the host you need to provide a way for the network cross the container boundary. Could you please help on this and may I know the minimum RAM requirment, where this LLM is running.

Soporte para configurar un bot de IA para un foro de comunidad de soporte con la última versión de Discourse

Soporte del producto

Falco (Falco) 4 Noviembre, 2025 19:10 7

Establezca el proveedor en OpenAI si está utilizando la API compatible con OpenAI de Ollama.

Tema		Respuestas	Vistas
Chat with forum via the AI Product Support ai , ai-bot	4	1131	15 Agosto 2023
Discourse AI - AI Bot - a glimpse of capabilities General ai , ai-bot	4	1525	22 Noviembre 2023
Discourse AI - AI bot Site Management how-to , ai , ai-bot	49	19974	1 Marzo 2026
Enhance or create a different AI bot to help Discourse developers Feature ai , ai-bot	0	476	20 Agosto 2023
[Ai Bot] Add user token tracking, custom AI personas, max context posts, document loading, custom API URLs, and localized chat titles Feature ai , ai-bot	1	815	22 Marzo 2024

Soporte para configurar un bot de IA para un foro de comunidad de soporte con la última versión de Discourse

Temas relacionados