# Can't enable DiscourseID on a site with force-https disabled

**URL:** https://meta.discourse.org/t/cant-enable-discourseid-on-a-site-with-force-https-disabled/399376
**Category:** Self-hosting
**Tags:** discourse-id
**Created:** [March 26, 2026, 8:29pm UTC](https://meta.discourse.org/t/cant-enable-discourseid-on-a-site-with-force-https-disabled/399376 "2026-03-26T20:29:27Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![darkpixlz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darkpixlz/32/549896_2.png) [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [March 26, 2026, 8:29pm UTC](https://meta.discourse.org/t/cant-enable-discourseid-on-a-site-with-force-https-disabled/399376/1 "2026-03-26T20:29:27Z")

</div>

For context, I have my Discourse test site running in a Proxmox container behind Nginx (npmplus) on a different server on the same network (but not subnet). Not really anything special. I tried enabling `force-https` but I kept getting a bunch of CSRF validation errors so I just disabled it again because it wasn’t worth a fight. Regardless of any of that, the site works on https fine because Nginx/Cloudflare are both set up for it properly:

 ![image](https://global.discourse-cdn.com/meta/original/4X/d/6/a/d6ab7e1dd79332f279a71f7485a849b1d754b6f1.png)

I tried enabling DiscorseID on the site just now but was met with an error:

 ![image](https://global.discourse-cdn.com/meta/original/4X/8/3/f/83fc018567ef53e9e0e398a091575de7027e1097.png)  
 ![image](https://global.discourse-cdn.com/meta/original/4X/9/3/2/9322fc450b2961af0eb37bbb8d92fe57ed67b7d3.png)

Is there a workaround that doesn’t involve fighting with npmplus for hours to get Discourse CSRF validation to stop complaining about anything? This thread is not for debugging npmplus or SSL, I simply want to fix Discourse ID.

---

_[View the full topic](https://meta.discourse.org/t/cant-enable-discourseid-on-a-site-with-force-https-disabled/399376)._