# Problem Responding a Topic

**URL:** https://meta.discourse.org/t/problem-responding-a-topic/297857
**Category:** Support
**Created:** [March 4, 2024, 6:36pm UTC](https://meta.discourse.org/t/problem-responding-a-topic/297857 "2024-03-04T18:36:06Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![rrodrigueznt](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rrodrigueznt/32/351504_2.png) [@rrodrigueznt](https://meta.discourse.org/u/rrodrigueznt)
#### Post date: [March 9, 2024, 5:40pm UTC](https://meta.discourse.org/t/problem-responding-a-topic/297857/3 "2024-03-09T17:40:34Z")

</div>

> [@Moin](#):
>
> the admin

Hi @Moin, all! Here “the admin”! Thanks for replying. Also thanks to @abdul19 for starting this thread.

@abdul19 and I are working to set up a _seed community_ on our research centre by using Discourse. Brief but great experience so far! Thanks for the hard work and for sharing! But we are also facing some issues also.

Our [Discourse instance](https://forum.igfae.usc.es) is running on an Ubuntu 22.04.4 LTS (Jammy) box, behind a Nginx reverse proxy server running on an AlmaLinux 9.3 (Shamrock Pampas Cat). It is up-to-date as per Upgrade several times a day (currently, 3.3.0.beta1-dev, latest-release +557)

Nginx configuration file for the site reads:

```plaintext
[rjr@e220i058h025lx sites-enabled]$ cat forum.conf
server {
    server_name forum.igfae.usc.es;

    location / {
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header Host $http_host;
        proxy_pass "http://172.16.57.96";
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/forum.igfae.usc.es/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/forum.igfae.usc.es/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}

server {
    if ($host = forum.igfae.usc.es) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    server_name forum.igfae.usc.es;
    listen 80;
    return 404; # managed by Certbot

}
[rjr@e220i058h025lx sites-enabled]$

```

Everything seemed to work fine until some days ago. I’m not able to remember the exact moment. Perhaps an upgrade, perhaps a change in settings. We started seeing mixed contents issues. Looking for a solution, we founded [this thread](https://meta.discourse.org/t/front-nginx-https-reverse-proxy-to-discourse-http/106000). Setting `force https` to `true`, solved mixed content errors, but we are not able to log in.

I think at some point we were not able to log out, reply or post: this was the moment @abdul19 created this thread.

Currently, if `force https` is set to true, we don’t get mixed contents errors, but users can’t log in. Already logged-in users, are fully operative. When trying to log, after clicking login, we get:

 ![DOM_Exception_Screenshot 2024-03-09 175205](https://global.discourse-cdn.com/meta/original/4X/2/7/9/279b9c77b304594fcd279c254ee874157b671aff.png)

If ‘force https’ is set to false, users can log in, but mixed content errors appear:

 ![Mixed_contents_Screenshot 2024-03-09 182333](https://global.discourse-cdn.com/meta/original/4X/7/5/5/755ed5f04f9d2ed002713418eb0ce3240976f479.png)

Does it make any sense for you? Could you guide us towards a solution? Could it me more suitable to create a new topic and link this post to it? Thanks!

---

_[View the full topic](https://meta.discourse.org/t/problem-responding-a-topic/297857)._