# Connection problems with nginx ssl reverse proxy

**URL:** <https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778>\
**Category:** Community Support\
**Created:** [August 20, 2025, 8:09am UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778 "2025-08-20T08:09:26Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![maks.yak](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@maks.yak](https://community.datagerry.com/u/maks.yak)\
**Post date:** [August 20, 2025, 8:09am UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/1 "2025-08-20T08:09:26Z")

</div>

Hello everyone.

I’m trying to install datagerry using docker compose. When I configure nginx with ssl, I see the following message:

“If you see this message, the frontend cannot find a connection to DATAGERRY. Probably there is a problem with your backend instance. You can try to connect manually. Otherwise notify your administrator.”

and connection status “DISCONNECTED”

When I specify the server address (192.168.1.123:443) in the connection details fields, the connection status becomes “CONNECTED” and I can continue working. But this must be specified in each browser.

Connection to 192.168.1.123:4000 works fine.

Please tell me where in the settings or ENV variables I need to specify the address to avoid this problem.

Thanks.

---

<div class="post-metadata">

**Author:** ![abdullah-khalid](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/abdullah-khalid/32/860_2.png) [@abdullah-khalid](https://community.datagerry.com/u/abdullah-khalid)\
**Post date:** [August 20, 2025, 11:41am UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/2 "2025-08-20T11:41:50Z")

</div>

Hi @maks.yak,

The DataGerry frontend remains **DISCONNECTED** until the user enters the backend server URL on the connection page. That needs to be done only **once per browser** —once set, the same browser will remember it for future sessions.

**Sincerely,**

Your DataGerry Team

---

<div class="post-metadata">

**Author:** ![maks.yak](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@maks.yak](https://community.datagerry.com/u/maks.yak)\
**Post date:** [August 20, 2025, 11:52am UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/3 "2025-08-20T11:52:10Z")

</div>

Thank you so much for explanation.

---

<div class="post-metadata">

**Author:** ![cmdbeval1](https://avatars.discourse-cdn.com/v4/letter/c/f14d63/32.png) [@cmdbeval1](https://community.datagerry.com/u/cmdbeval1)\
**Post date:** [August 20, 2025, 1:01pm UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/4 "2025-08-20T13:01:23Z")

</div>

Same problem/workaround here.

I do not understand WHY a normal user should be forced to enter such technical details even only at the first usage.

@abdullah-khalid

Could you please permanently fix this as a programmer?

Thank you

---

<div class="post-metadata">

**Author:** ![abdullah-khalid](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/abdullah-khalid/32/860_2.png) [@abdullah-khalid](https://community.datagerry.com/u/abdullah-khalid)\
**Post date:** [August 22, 2025, 8:16am UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/5 "2025-08-22T08:16:46Z")

</div>

Hi @cmdbeval1@maks.yak ,

I’ve spoken with our package team and it turns out there’s currently an issue with our SSL setup. We’re actively fixing it and will resolve this as soon as possible. In the meantime, please use the HTTP (non-SSL). Thanks for your patience!

**Sincerely,**

Your DataGerry Team

---

<div class="post-metadata">

**Author:** ![Swordfish](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/swordfish/32/756_2.png) [@Swordfish](https://community.datagerry.com/u/Swordfish)\
**Post date:** [August 25, 2025, 9:20am UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/6 "2025-08-25T09:20:43Z")

</div>

The problem also exists with the standalone installation without Docker.

We fixed it by having nginx listen on port 4000 and datagerry itself on port 8080.

nginx:

```bash
upstream datagerry_backend {
    least_conn;
    server 127.0.0.1:8080;
}
server {
    server_name gerry.example.com;
    listen *:80;

    location / {
        return 301 https://$host$request_uri;
    }
}
server {
    listen *:443 ssl;
    listen *:4000 ssl;
    server_name gerry.example.com;

    location / {
        proxy_redirect off;
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_read_timeout 600;
	    proxy_pass http://datagerry_backend/;
	    resolver 10.10.32.10 10.10.32.11 ipv6=off valid=30s;
        rewrite ^/(.*) /$1 break;
    }
    include /etc/nginx/ssl.conf;
    ssl_certificate /etc/ssl/certs/wildcard_example_com.crt;
    ssl_certificate_key /etc/ssl/private/wildcard_example_com.key;
}

```

cmdb.conf

```bash
[WebServer]
host = 127.0.0.1
port = 8080

```

---

<div class="post-metadata">

**Author:** ![MirjamSWS](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@MirjamSWS](https://community.datagerry.com/u/MirjamSWS)\
**Post date:** [January 20, 2026, 2:43pm UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/7 "2026-01-20T14:43:33Z")

</div>

Is there any ETA for a fix? Still fiddling about with 2.2 here because of this..

---

<div class="post-metadata">

**Author:** ![bettina.mauz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/bettina.mauz/32/940_2.png) [@bettina.mauz](https://community.datagerry.com/u/bettina.mauz)\
**Post date:** [January 21, 2026, 9:40am UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/8 "2026-01-21T09:40:09Z")

</div>

Hi @MirjamSWS ,

we will discuss this topic next week and will keep you up to date here.

Sincerely,

Your DataGerry Team

---

<div class="post-metadata">

**Author:** ![bettina.mauz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/bettina.mauz/32/940_2.png) [@bettina.mauz](https://community.datagerry.com/u/bettina.mauz)\
**Post date:** [February 6, 2026, 11:41am UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/9 "2026-02-06T11:41:56Z")

</div>

Hi @MirjamSWS ,

this fix will be part of the next release, which is scheduled for 14 February 2026.

Sincerely,

Your DataGerry Team

---

<div class="post-metadata">

**Author:** ![amos](https://avatars.discourse-cdn.com/v4/letter/a/ebca7d/32.png) [@amos](https://community.datagerry.com/u/amos)\
**Post date:** [February 18, 2026, 9:10am UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/10 "2026-02-18T09:10:41Z")

</div>

Hello Team,

I started to use DataGerry 3.1, and I still get the “connection” page stated above.

What is the reason for getting this page ? Can you please give me a detailed guideline how to avoid getting it ? is it related to some missing SSL configuration in nginx ?

Thank You

Amos

---

<div class="post-metadata">

**Author:** ![bettina.mauz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/bettina.mauz/32/940_2.png) [@bettina.mauz](https://community.datagerry.com/u/bettina.mauz)\
**Post date:** [February 19, 2026, 9:12am UTC](https://community.datagerry.com/t/connection-problems-with-nginx-ssl-reverse-proxy/778/11 "2026-02-19T09:12:56Z")

</div>

Hi @amos ,

you will find a detailed installation guide for setting up Datagerry Docker with SSL here:

> **[Setup via Docker Image - On-Premises Installation — DataGerry latest...](https://docs.datagerry.com/en/latest/getting_started/dg_installation.html#setup-via-docker-image)**
>
> This page provides a detailed overview of how to install DataGerry on various operating systems and platforms.

The connection page shouldn’t appear, after the described configuration steps.

Sincerely,

Your DataGerry Team