Connection problems with nginx ssl reverse proxy

Community Support
1

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.

2

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

3

Thank you so much for explanation.

4

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

2 Likes
5

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

6

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:

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

[WebServer]
host = 127.0.0.1
port = 8080
1 Like
7

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

1 Like
8

Hi @MirjamSWS ,

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

Sincerely,

Your DataGerry Team

1 Like
9

Hi @MirjamSWS ,

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

Sincerely,

Your DataGerry Team

10

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

11

Hi @amos ,

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

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

Sincerely,

Your DataGerry Team