ac92567 fix: pass verify=False at httpx client construction for MCP SSL bypass
📊 Changes
1 file changed (+17 additions, -4 deletions)
View changed files
📝backend/open_webui/utils/mcp/client.py (+17 -4)
📄 Description
Setting client.verify = False after httpx.AsyncClient construction does not affect the underlying transport's SSL context - the SSL context is configured during init and cannot be changed afterward. This caused MCP tool connections to always verify SSL certificates even when AIOHTTP_CLIENT_SESSION_TOOL_SERVER_SSL was set to false.
Build the httpx.AsyncClient directly with verify=False in the constructor kwargs to properly disable SSL certificate verification.
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.
Note
Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/open-webui/open-webui/pull/21485
**Author:** [@Classic298](https://github.com/Classic298)
**Created:** 2/16/2026
**Status:** ✅ Merged
**Merged:** 2/19/2026
**Merged by:** [@tjbck](https://github.com/tjbck)
**Base:** `dev` ← **Head:** `claude/fix-mcp-ssl-check-0janH`
---
### 📝 Commits (1)
- [`ac92567`](https://github.com/open-webui/open-webui/commit/ac925677f85d2ca88cf640a2f865c85e7dd1350d) fix: pass verify=False at httpx client construction for MCP SSL bypass
### 📊 Changes
**1 file changed** (+17 additions, -4 deletions)
<details>
<summary>View changed files</summary>
📝 `backend/open_webui/utils/mcp/client.py` (+17 -4)
</details>
### 📄 Description
Setting client.verify = False after httpx.AsyncClient construction does not affect the underlying transport's SSL context - the SSL context is configured during __init__ and cannot be changed afterward. This caused MCP tool connections to always verify SSL certificates even when AIOHTTP_CLIENT_SESSION_TOOL_SERVER_SSL was set to false.
Build the httpx.AsyncClient directly with verify=False in the constructor kwargs to properly disable SSL certificate verification.
Fixes #21481
### Contributor License Agreement
<!--
🚨 DO NOT DELETE THE TEXT BELOW 🚨
Keep the "Contributor License Agreement" confirmation text intact.
Deleting it will trigger the CLA-Bot to INVALIDATE your PR.
-->
By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms.
> [!NOTE]
> Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/21485
Author: @Classic298
Created: 2/16/2026
Status: ✅ Merged
Merged: 2/19/2026
Merged by: @tjbck
Base:
dev← Head:claude/fix-mcp-ssl-check-0janH📝 Commits (1)
ac92567fix: pass verify=False at httpx client construction for MCP SSL bypass📊 Changes
1 file changed (+17 additions, -4 deletions)
View changed files
📝
backend/open_webui/utils/mcp/client.py(+17 -4)📄 Description
Setting client.verify = False after httpx.AsyncClient construction does not affect the underlying transport's SSL context - the SSL context is configured during init and cannot be changed afterward. This caused MCP tool connections to always verify SSL certificates even when AIOHTTP_CLIENT_SESSION_TOOL_SERVER_SSL was set to false.
Build the httpx.AsyncClient directly with verify=False in the constructor kwargs to properly disable SSL certificate verification.
Fixes #21481
Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.