# Discourse AI causing new SSL and Connection Reset by Peer errors **URL:** \ **Category:** Bug\ **Tags:** ai\ **Created:** [February 21, 2025, 1:21pm UTC](https://meta.discourse.org/t/discourse-ai-causing-new-ssl-and-connection-reset-by-peer-errors/353600 "2025-02-21T13:21:26Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![oznyet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/oznyet/32/489947_2.png) [@oznyet](https://meta.discourse.org/u/oznyet)\ **Post date:** [February 25, 2025, 10:05am UTC](https://meta.discourse.org/t/discourse-ai-causing-new-ssl-and-connection-reset-by-peer-errors/353600/7 "2025-02-25T10:05:23Z")
> [@sam](#): > > I fixed the regression around o1-mini and o1-preview here: > > [FIX: legacy reasoning models not working, missing provider params by SamSaffron · Pull Request #1149 · discourse/discourse-ai · GitHub](https://github.com/discourse/discourse-ai/pull/1149) That’s awesome! Nicely done! In the process of diagnosing, I have found another bug - on the LLM config page (`/admin/plugins/discourse-ai/ai-llms/%/edit`), selecting either option to _“Disable native tool support (use XML based tools) (optional)”_ or _“Disable streaming completions (convert streaming to non streaming requests)”_ and clicking Save shows a “Success!” temporary toast, but then reloading the page has both or either option unchecked. The connection reset issues still persist and I am still digging into it, however it looks like a combination of the Ruby code (FinalDestination / DNS resolution / Faraday) socket handling, combined with Debian 12 container on a Ubuntu 24.04 VM. I have spun up a test Ubuntu 22.04 VM and there are no issues, all the embeddings and inference work perfectly. Have not seen a single reset. I’ll keep chipping away at it, perhaps it’s related to a novel way that Ubuntu 24.04 manages the tcp stack w/ netplan. --- _[View the full topic](https://meta.discourse.org/t/discourse-ai-causing-new-ssl-and-connection-reset-by-peer-errors/353600)._