[GH-ISSUE #21093] feat: Native SSL/TLS support. #34908

New Issue

GiteaMirror · 2026-04-25T09:05:12-05:00

GiteaMirror commented

2026-04-25 09:05:12 -05:00

Originally created by @abcbarryn on GitHub (Feb 1, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21093

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

It would be nice if there was a way to enable SSL/TLS for Open WebUI without using external solutions like stunnel, etc. Or am I missing something?

Desired Solution you'd like

I would like an option for Open WebUI to support https.

Alternatives Considered

I am currently running stunnel to supply https.

Additional Context

No response

Originally created by @abcbarryn on GitHub (Feb 1, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21093 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description It would be nice if there was a way to enable SSL/TLS for Open WebUI without using external solutions like stunnel, etc. Or am I missing something? ### Desired Solution you'd like I would like an option for Open WebUI to support https. ### Alternatives Considered I am currently running stunnel to supply https. ### Additional Context _No response_

GiteaMirror closed this issue

2026-04-25 09:05:12 -05:00

GiteaMirror commented

2026-04-25 09:05:13 -05:00

@TomTheWise commented on GitHub (Feb 2, 2026):

It is VERY standard for Web Applications to always put them behind reverseproxies like apache2 or nginx which then handle the TLS termination and proxy their requests to the actual application.

For example tomcat / jetty based enterprise Java web apps are typically put behind reverse proxies - simply for example to strengthen the security and other reasons.

Also this allows for some of the SSO features. With Apache2 you can for example do Kerberos based SSO or other authentication types and then pass on and use the email header provided from the Apache2 in OpenWebUI for authentication.

So, as to me this is very standard practice for enterprise web applications, I doubt that native TLS would be a worthy addition.

@TomTheWise commented on GitHub (Feb 2, 2026): It is VERY standard for Web Applications to always put them behind reverseproxies like apache2 or nginx which then handle the TLS termination and proxy their requests to the actual application. For example tomcat / jetty based enterprise Java web apps are typically put behind reverse proxies - simply for example to strengthen the security and other reasons. Also this allows for some of the SSO features. With Apache2 you can for example do Kerberos based SSO or other authentication types and then pass on and use the email header provided from the Apache2 in OpenWebUI for authentication. So, as to me this is very standard practice for enterprise web applications, I doubt that native TLS would be a worthy addition.

GiteaMirror commented

2026-04-25 09:05:13 -05:00

@Classic298 commented on GitHub (Feb 2, 2026):

I dont think this will be implemented and I didn't close this issue yet because this, i don't want to decide, here tim should have the last word.

But if anyone is landing here from search or else: there are many and very good tutorials in the docs for how to set up various reverse proxies. It's simple, gives you full control over how the data is served, even improves loading speed through caching - and also implements TLS support if you need it.

And yeah, in enterprise scenario it is absolutely standard to put a reverse proxy in front of the application - for security reasons, but also for load balancing, caching and more.
Security definitely being a major point here

@Classic298 commented on GitHub (Feb 2, 2026): I dont think this will be implemented and I didn't close this issue yet because this, i don't want to decide, here tim should have the last word. But if anyone is landing here from search or else: there are many and very good tutorials in the docs for how to set up various reverse proxies. It's simple, gives you full control over how the data is served, even improves loading speed through caching - and also implements TLS support if you need it. And yeah, in enterprise scenario it is absolutely standard to put a reverse proxy in front of the application - for security reasons, but also for load balancing, caching and more. Security definitely being a major point here

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#34908