Hey there. Some frustration setting up instances of open source projects in my environment I am used to, but this is my champion. No information to be found on the errors I get. I may be the first one, though corteza is not my first one. Sheâs a winner.
Letâs start with this, the first messages of my âserverâ (corredor & webserver?):
{âlevelâ:âwarnâ,âtsâ:1690641554.7411294,âmsgâ:âYouâre using SQLite as a storage backendâ}
{âlevelâ:âwarnâ,âtsâ:1690641554.7413898,âmsgâ:âShould be used only for testingâ}
{âlevelâ:âwarnâ,âtsâ:1690641554.7414382,âmsgâ:âYou may experience instability and data lossâ}
{âlevelâ:âwarnâ,âtsâ:1690641556.018052,âmsgâ:âno SMTP servers found, email sending will be disabledâ}
That is very strange since to begin with, I am using postgres in the way it is being described in the DevOp documentation. It gave some hickups I was able to solve but postgresql starts and is ready for a connection. I guess I can also see no connection is being made:
PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-07-29 14:39:14.315 UTC [1] LOG: starting PostgreSQL 13.11 (Debian 13.11-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2023-07-29 14:39:14.315 UTC [1] LOG: listening on IPv4 address â0.0.0.0â, port 5432
2023-07-29 14:39:14.316 UTC [1] LOG: listening on IPv6 address â::â, port 5432
2023-07-29 14:39:14.318 UTC [1] LOG: listening on Unix socket â/var/run/postgresql/.s.PGSQL.5432â
2023-07-29 14:39:14.324 UTC [28] LOG: database system was shut down at 2023-07-29 14:39:12 UTC
2023-07-29 14:39:14.334 UTC [1] LOG: database system is ready to accept connections
Thatâs it. Nothing else ever happens here. But former âmsgâ is explanatory. For sure.
Next it is quite strange the start log of the âserver(?)â, (â> by the way I had enough troubleshooting time to get a brief overview of cortezaâs historic ways of building the Docker container & check the most recent dockerfile(s) to analyse if I could change something there. Which I donât like if the âdocsâ seem so professional, up to date and clear), this start states it canât find an smtp server. Very strange. Other webapps use the same and find it flawlessly. So: did I use the .env file the right way? Well; I added the info as it was explained in the devop docs and I must say: the VERSION= , from the .env works perfectly. (Unless I change the .env fileâs name. If I do that docker-compose doesnât want me start up with a clear log message).
But letâs say I donât want to work with email. Then newly created users are marked active by default. So letâs try to login. The url mentioned in the .env takes me to http://localhost/auth/oauth2/xxxxx. Useless. My w10 IIS doesnât know anything. And I canât find anywhere where I ask for any local address. Maybe this is where Traefik misses something that nginx would find. Very unfortunate I canât find anything about this eratic behavior except something about the oauth implementation that could be called recent. Maybe that is a lead?
Funny enough going to https://mydomain.org/auth, I DO go to the login page. So there is some webserver running to serve me that page (it makes me happy). But logging in is impossible. A glitch in the login page is all I get. From login page to login page. *glitch
Well. A very short new topic compared to everything I tried to figure out how this app is meant to be served out. I hope there are some people here with enough knowledge of the main system to find out with me why .env variables donât seem to be picked up ( at least some donât) and how using Traefik influences the way I should get to a working first install.
For sur: Many Thanks in advance!
P.S. https://my-domain.org/healthcheck seems to tell a different story (especially about the email)
PASS Scheduler
PASS Mail
PASS Corredor
PASS Primary store
PASS ObjectStore/System
PASS ObjectStore/Compose