On Premise: After setting up production web returns "Connection to server timed out"

Created August 30, 2023 10:45

Hello,

after going through this documentation: https://www.jetbrains.com/help/space/configure-space-for-docker-compose-production-environment.html I ended up after login screen with this:

On server are some errors that I don't understand and don't know how to fix it.

public.registry.jetbrains.space/p/space-on-premises/docker/space:2023.2.0

root@server /s/a/space-on-premises# docker logs 3a8ff3f1ca11 | grep ERROR
2023-08-30 10:01:51.531 [ktor-server-jetty-273] ERROR Application [dbType=postgresql, trace_id=7273053243568072032, orgDomain=space, orgId=3140828502057818121, dbKey=postgres] - Websocket handler failed
2023-08-30 10:01:58.963 [ktor-server-jetty-275] ERROR Application [dbType=postgresql, trace_id=7273053351076604728, orgDomain=space, orgId=3140828502057818121, dbKey=postgres] - Websocket handler failed

public.registry.jetbrains.space/p/space-on-premises/docker/vcs-hosting:2023.2.0

root@server /s/a/space-on-premises# docker logs 983b8061b150 | grep ERROR
[2023-08-30 10:33:29,913]  ERROR [or-jetty-8080-1]                                                            Application - Unhandled exception caught for CoroutineName(jetty-call-handler)

public.registry.jetbrains.space/p/space-on-premises/docker/packages:2023.2.0

root@server /s/a/space-on-premises# docker logs f2d2abc1fa9e | grep ERROR
[2023-08-30 09:55:28,504]  ERROR [-pool] shared-3]       circlet.platform.a.l.c.e [dbType=postgresql, trace_id=7273051783170994464, txOriginName=ApplicationLifecycle:startServices:circlet.packages.server.db.PackagesMetaDBConnection:create locks table and check schema, dbKey=postgres] - Deployment branch was not specified for production environment, env value is null
[2023-08-30 10:17:43,384]  ERROR [-pool] shared-3]       circlet.platform.a.l.c.e [dbType=postgresql, trace_id=7273057516946146641, txOriginName=ApplicationLifecycle:startServices:circlet.packages.server.db.PackagesMetaDBConnection:create locks table and check schema, dbKey=postgres] - Deployment branch was not specified for production environment, env value is null

4 comments

Pavel Boger

Created August 30, 2023 13:19

Jan Zenisek thanks for reporting this! Could you please share the entire logs from all Space containers? Please also share your nginx configuration if it differs from the one provided in our guide. Looking forward to hearing from you soon!

Jan Zenisek

Created August 30, 2023 13:50

Ok, docker-compose logs are here (its too big), and there is nginx configuration:

server {
    client_max_body_size 0;
    server_name space.example.com;
    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;
        proxy_pass http://127.0.0.1:8084/;
        proxy_redirect off;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }

    listen 443 ssl;
    ssl_certificate /etc/letsencrypt/live/space.example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/space.example.com/privkey.pem;
}

server {
    client_max_body_size 0;
    server_name git.example.com;
    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;
        proxy_pass http://127.0.0.1:8080/;
        proxy_redirect off;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }

    listen 443 ssl;
    ssl_certificate /etc/letsencrypt/live/git.example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/git.example.com/privkey.pem;
}

server {
    client_max_body_size 0;
    server_name packages.example.com;
    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;
        proxy_pass http://127.0.0.1:8390/;
        proxy_redirect off;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }

    listen 443 ssl;
    ssl_certificate /etc/letsencrypt/live/packages.example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/packages.example.com/privkey.pem;
}

server {
    client_max_body_size 0;
    server_name minio.example.com;
    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;
        proxy_pass http://127.0.0.1:9000/;
        proxy_redirect off;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }

    listen 443 ssl;
    ssl_certificate /etc/letsencrypt/live/minio.example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/minio.example.com/privkey.pem;
}

# configuring HTTP redirects

server {
    if ($host = space.example.com) {
        return 301 https://$host$request_uri;
    }

    server_name space.example.com;
    listen 80;
    return 404;
}

server {
    if ($host = git.example.com) {
        return 301 https://$host$request_uri;
    }

    server_name git.example.com;
    listen 80;
    return 404;
}

server {
    if ($host = packages.example.com) {
        return 301 https://$host$request_uri;
    }

    server_name packages.example.com;
    listen 80;
    return 404;
}

server {
    if ($host = minio.example.com) {
        return 301 https://$host$request_uri;
    }

    server_name minio.example.com;
    listen 80;
    return 404;
}

Jan Zenisek

Created August 30, 2023 16:51

I found one oddity, in Firefox it reports me an error even on jetbrains.space, but when I open both my instance or cloud in another browser or in anonymous mode in Firefox, it works normally. I have AdBlock turned off.

Pavel Boger

Created August 31, 2023 08:19

Thanks for this information! May I ask if you tried to clear the cache and other site data? Are there any other extensions enabled for your default browser?

Please sign in to leave a comment.