Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Windmill Service One-Click Setup displays net::ERR_CERT_AUTHORITY_INVALID error #3960

Open
atilladeniz opened this issue Oct 20, 2024 · 3 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@atilladeniz
Copy link

Error Message and Logs

This is not a secure connection
Attackers might be trying to steal your information from ..., such as passwords, messages, or credit card details. More information about this warning
net::ERR_CERT_AUTHORITY_INVALID

DB Logs:

2024-10-20T10:44:11.084243413Z The files belonging to this database system will be owned by user "postgres". 2024-10-20T10:44:11.084311654Z This user must also own the server process. 2024-10-20T10:44:11.084317844Z 2024-10-20T10:44:11.084420495Z The database cluster will be initialized with locale "en_US.utf8". 2024-10-20T10:44:11.084556607Z The default database encoding has accordingly been set to "UTF8". 2024-10-20T10:44:11.084565007Z The default text search configuration will be set to "english". 2024-10-20T10:44:11.084568056Z 2024-10-20T10:44:11.084570717Z Data page checksums are disabled. 2024-10-20T10:44:11.084652547Z 2024-10-20T10:44:11.084773278Z fixing permissions on existing directory /var/lib/postgresql/data ... ok 2024-10-20T10:44:11.085284814Z creating subdirectories ... ok 2024-10-20T10:44:11.085475895Z selecting dynamic shared memory implementation ... posix 2024-10-20T10:44:11.104222078Z selecting default max_connections ... 100 2024-10-20T10:44:11.126145900Z selecting default shared_buffers ... 128MB 2024-10-20T10:44:11.142988885Z selecting default time zone ... Etc/UTC 2024-10-20T10:44:11.143710892Z creating configuration files ... ok 2024-10-20T10:44:11.265682007Z running bootstrap script ... ok 2024-10-20T10:44:11.619371055Z performing post-bootstrap initialization ... ok 2024-10-20T10:44:11.713256587Z syncing data to disk ... ok 2024-10-20T10:44:11.713293667Z 2024-10-20T10:44:11.713296947Z 2024-10-20T10:44:11.713299837Z Success. You can now start the database server using: 2024-10-20T10:44:11.713302237Z 2024-10-20T10:44:11.713304427Z pg_ctl -D /var/lib/postgresql/data -l logfile start 2024-10-20T10:44:11.713306747Z 2024-10-20T10:44:11.713322928Z initdb: warning: enabling "trust" authentication for local connections 2024-10-20T10:44:11.713362918Z initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. 2024-10-20T10:44:11.772191269Z waiting for server to start....2024-10-20 10:44:11.772 UTC [48] LOG: starting PostgreSQL 16.4 (Debian 16.4-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit 2024-10-20T10:44:11.776117489Z 2024-10-20 10:44:11.775 UTC [48] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2024-10-20T10:44:11.781355779Z 2024-10-20 10:44:11.781 UTC [51] LOG: database system was shut down at 2024-10-20 10:44:11 UTC 2024-10-20T10:44:11.786187156Z 2024-10-20 10:44:11.786 UTC [48] LOG: database system is ready to accept connections 2024-10-20T10:44:11.853033175Z done 2024-10-20T10:44:11.853090086Z server started 2024-10-20T10:44:11.989680074Z CREATE DATABASE 2024-10-20T10:44:11.990869445Z 2024-10-20T10:44:11.991008027Z 2024-10-20T10:44:11.991157138Z /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/* 2024-10-20T10:44:11.991164908Z 2024-10-20T10:44:11.992445441Z waiting for server to shut down....2024-10-20 10:44:11.992 UTC [48] LOG: received fast shutdown request 2024-10-20T10:44:11.994540321Z 2024-10-20 10:44:11.994 UTC [48] LOG: aborting any active transactions 2024-10-20T10:44:11.997082516Z 2024-10-20 10:44:11.996 UTC [48] LOG: background worker "logical replication launcher" (PID 54) exited with exit code 1 2024-10-20T10:44:11.999032975Z 2024-10-20 10:44:11.998 UTC [49] LOG: shutting down 2024-10-20T10:44:12.000326778Z 2024-10-20 10:44:12.000 UTC [49] LOG: checkpoint starting: shutdown immediate 2024-10-20T10:44:12.034147666Z 2024-10-20 10:44:12.033 UTC [49] LOG: checkpoint complete: wrote 922 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.014 s, sync=0.016 s, total=0.036 s; sync files=301, longest=0.003 s, average=0.001 s; distance=4255 kB, estimate=4255 kB; lsn=0/1912108, redo lsn=0/1912108 2024-10-20T10:44:12.040754739Z 2024-10-20 10:44:12.040 UTC [48] LOG: database system is shut down 2024-10-20T10:44:12.092742315Z done 2024-10-20T10:44:12.092773305Z server stopped 2024-10-20T10:44:12.094962866Z 2024-10-20T10:44:12.094996727Z PostgreSQL init process complete; ready for start up. 2024-10-20T10:44:12.094999347Z 2024-10-20T10:44:12.119926739Z 2024-10-20 10:44:12.119 UTC [1] LOG: starting PostgreSQL 16.4 (Debian 16.4-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit 2024-10-20T10:44:12.120147380Z 2024-10-20 10:44:12.120 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 2024-10-20T10:44:12.121080380Z 2024-10-20 10:44:12.120 UTC [1] LOG: listening on IPv6 address "::", port 5432 2024-10-20T10:44:12.123225470Z 2024-10-20 10:44:12.123 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2024-10-20T10:44:12.127268331Z 2024-10-20 10:44:12.127 UTC [64] LOG: database system was shut down at 2024-10-20 10:44:12 UTC 2024-10-20T10:44:12.132804094Z 2024-10-20 10:44:12.132 UTC [1] LOG: database system is ready to accept connections 2024-10-20T10:44:21.981301342Z 2024-10-20 10:44:21.981 UTC [76] ERROR: relation "windmill_migrations" does not exist at character 32 2024-10-20T10:44:21.981317782Z 2024-10-20 10:44:21.981 UTC [76] STATEMENT: SELECT EXISTS(SELECT name FROM windmill_migrations WHERE name = 'fix_flow_versioning_2') 2024-10-20T10:44:21.989214858Z 2024-10-20 10:44:21.988 UTC [77] ERROR: relation "windmill_migrations" does not exist at character 32 2024-10-20T10:44:21.989236789Z 2024-10-20 10:44:21.988 UTC [77] STATEMENT: SELECT EXISTS(SELECT name FROM windmill_migrations WHERE name = $1) 2024-10-20T10:44:22.069117365Z 2024-10-20 10:44:22.068 UTC [79] ERROR: relation "windmill_migrations" does not exist at character 32 2024-10-20T10:44:22.069131736Z 2024-10-20 10:44:22.068 UTC [79] STATEMENT: SELECT EXISTS(SELECT name FROM windmill_migrations WHERE name = 'fix_flow_versioning_2') 2024-10-20T10:44:22.073930042Z 2024-10-20 10:44:22.073 UTC [80] ERROR: relation "windmill_migrations" does not exist at character 32 2024-10-20T10:44:22.081620416Z 2024-10-20 10:44:22.073 UTC [80] STATEMENT: SELECT EXISTS(SELECT name FROM windmill_migrations WHERE name = $1) 2024-10-20T10:44:22.117382989Z 2024-10-20 10:44:22.116 UTC [82] ERROR: relation "windmill_migrations" does not exist at character 32 2024-10-20T10:44:22.117394649Z 2024-10-20 10:44:22.116 UTC [82] STATEMENT: SELECT EXISTS(SELECT name FROM windmill_migrations WHERE name = 'fix_flow_versioning_2') 2024-10-20T10:44:22.140965176Z 2024-10-20 10:44:22.140 UTC [85] ERROR: relation "windmill_migrations" does not exist at character 32 2024-10-20T10:44:22.140986745Z 2024-10-20 10:44:22.140 UTC [85] STATEMENT: SELECT EXISTS(SELECT name FROM windmill_migrations WHERE name = $1) 2024-10-20T10:44:22.185342702Z 2024-10-20 10:44:22.179 UTC [86] ERROR: relation "windmill_migrations" does not exist at character 32 2024-10-20T10:44:22.185355871Z 2024-10-20 10:44:22.179 UTC [86] STATEMENT: SELECT EXISTS(SELECT name FROM windmill_migrations WHERE name = 'fix_flow_versioning_2') 2024-10-20T10:44:22.204795078Z 2024-10-20 10:44:22.203 UTC [90] ERROR: relation "windmill_migrations" does not exist at character 32 2024-10-20T10:44:22.204804378Z 2024-10-20 10:44:22.203 UTC [90] STATEMENT: SELECT EXISTS(SELECT name FROM windmill_migrations WHERE name = $1) 2024-10-20T10:44:22.215956125Z 2024-10-20 10:44:22.215 UTC [89] ERROR: relation "windmill_migrations" does not exist at character 32 2024-10-20T10:44:22.215975105Z 2024-10-20 10:44:22.215 UTC [89] STATEMENT: SELECT EXISTS(SELECT name FROM windmill_migrations WHERE name = 'fix_flow_versioning_2') 2024-10-20T10:44:22.216426610Z 2024-10-20 10:44:22.216 UTC [91] ERROR: relation "windmill_migrations" does not exist at character 32 2024-10-20T10:44:22.216472811Z 2024-10-20 10:44:22.216 UTC [91] STATEMENT: SELECT EXISTS(SELECT name FROM windmill_migrations WHERE name = $1)

Steps to Reproduce

  1. Add a new service
  2. Install Windmill using the One-Click Setup
  3. Once the health check shows "Running"

CleanShot 2024-10-20 at 12 45 31@2x

CleanShot 2024-10-20 at 12 46 42@2x

Example Repository URL

No response

Coolify Version

v4.0.0-beta.360

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 22.04

Additional Information

No response

@atilladeniz atilladeniz added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Oct 20, 2024
@draylegend
Copy link

Not sure if my problem can be listed hier. I'm getting

net::ERR_CERT_AUTHORITY_INVALID
Subject: TRAEFIK DEFAULT CERT

Issuer: TRAEFIK DEFAULT CERT

Expires on: Oct 21, 2025

Current date: Oct 21, 2024

PEM encoded chain:
-----BEGIN CERTIFICATE-----
MIIDXjCCAkagAwIBAgIRAOa0gMpYPe3I+t+cyLramDQwDQYJKoZIhvcNAQELBQAw
...
-----END CERTIFICATE-----

For some reason it doesn't sign correctly.

Screenshots

Actual:

image

Expected:

image

Thank you very much for help in advance! ❤️‍🔥

@atilladeniz
Copy link
Author

Hey @draylegend,

We’ve confirmed that the following YAML configuration works seamlessly with Docker Compose:

https://github.com/coollabsio/coolify/blob/341c7e359818fca86680819f4359c25ad7dd659b/templates/compose/windmill.yaml

The previous version mainly requires attention to setting the password in the environment variables. Everything else remains consistent.

@draylegend
Copy link

draylegend commented Oct 21, 2024

@atilladeniz thank you for your response, but the coolify instance itself can't be accessed via configured domain. In my case https://coolify.my-awesome-app.io. Only via IP. I don't use windmill. Should I create new issue?

I think I found related issue #3902

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Development

No branches or pull requests

2 participants