ERR_CONNECTION_REFUSED after fresh installation

🚧 Installation
#1

Hi, I deployed Corteza offline according to instructions on Windows 10 with Docker Desktop & compose.

While trying to visit the http://localhost:18080 for the first time, I get the ERR_CONNECTION_REFUSED from the browser, where URL is

http://localhost:18083/auth/oauth2/default-client?redirect_uri=http://localhost:18080/auth/callback&scope=profile%20api&state=8a83xh49zy

The output from running the container is

my-corteza-server-1 | {"level":"warn","ts":1664653771.914734,"logger":"http.apigw","msg":"profiler enabled only for routes with a profiler prefilter, use global setting to enable for all (APIGW_PROFILER_GLOBAL)"}
my-corteza-db-1 | 
my-corteza-db-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
my-corteza-db-1 | 
my-corteza-db-1 | 2022-10-01 19:49:31.521 UTC [1] LOG:  starting PostgreSQL 13.8 (Debian 13.8-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
my-corteza-db-1 | 2022-10-01 19:49:31.521 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
my-corteza-db-1 | 2022-10-01 19:49:31.521 UTC [1] LOG:  listening on IPv6 address "::", port 5432
my-corteza-db-1 | 2022-10-01 19:49:31.526 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
my-corteza-db-1 | 2022-10-01 19:49:31.533 UTC [27] LOG:  database system was shut down at 2022-10-01 19:06:09 UTC
my-corteza-db-1 | 2022-10-01 19:49:31.537 UTC [1] LOG:  database system is ready to accept connections

The Windows firewall is off. What can be done?

Thanks.

#2

Additionally, I checked the version, which gives

{"response":{"buildTime":"2022-10-03T19:14:21Z","version":"2022.3.3"}}

healthcheck

PASS Scheduler
PASS Mail
PASS Corredor
PASS Store/RDBMS/postgres
PASS ObjectStore/System
PASS ObjectStore/Compose

and /api/docs are displayed. I also enabled Server Web Console and by using default log settings everything seems normal, without errors except a warning

profiler enabled only for routes with a profiler prefilter, use global setting to enable for all (APIGW_PROFILER_GLOBAL)

Still, I cannot make a first log in.

#3

Ahh… In DevOps Guide, under Offline deployment, Configure .env the DOMAIN parameter is wrongfully set as localhost:18083, and not as localhost:18080 as it should.

Problem solved. I wonder, why the example .env file is using the 18083 port number.

2 Likes
#4

Probably a mistake. Will fix the docs. Thanks for finding and reporting this.

2 Likes