# VirtualMin and SSL
**URL:** https://meta.discourse.org/t/virtualmin-and-ssl/301933
**Category:** Support
**Created:** [April 1, 2024, 8:19pm UTC](https://meta.discourse.org/t/virtualmin-and-ssl/301933 "2024-04-01T20:19:45Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@alchitry](https://meta.discourse.org/u/alchitry)
#### Post date: [April 1, 2024, 8:19pm UTC](https://meta.discourse.org/t/virtualmin-and-ssl/301933/1 "2024-04-01T20:19:45Z")
I’ve installed Discourse on my server running Virtualmin following this guide [How to install Discourse alongside Virtualmin - Virtualmin - Virtualmin Community](https://forum.virtualmin.com/t/how-to-install-discourse-alongside-virtualmin/124531)
Everything is working (including https) but if I enable force\_https in the Discourse settings everything breaks. Login doesn’t work and 403 errors are thrown for a lot of other operations.
I saw the same behavior as [Forced https deactivate](https://meta.discourse.org/t/forced-https-deactivate/123711)
I got things working again by disabling force\_https via the rails console. However, discourse seems to be using http for some links causing the mixed content warning.
I’d like to enable it.
I think the problem is with Apache handling the SSL stuff instead of Discourse but I couldn’t find anything about configuring one or the other to make them work together.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 1, 2024, 9:26pm UTC](https://meta.discourse.org/t/virtualmin-and-ssl/301933/2 "2024-04-01T21:26:49Z")
It’s hard to guess since Virtualmin isn’t supported here. You should ask the people who are using Virtualmin if they have solved that problem. Glancing at the topic you linked, though, it appears that everyone else has had trouble with https.
> [@Forced https deactivate](https://meta.discourse.org/t/forced-https-deactivate/123711/1):
>
> How can I deactivate force https if the login no longer works?
Maybe this is the issue you’re trying to solve? Once your browser has been told to insist on https, it’s hard to change its mind. You might be able to clear your, uh, stuff, to get it to forget the 301 redirect. You can try an incognito window or another browser.
Discourse won’t work without https, though, so you likely still won’t have a functioning site if you do manage to deactivate https.