this post was submitted on 09 Feb 2025
4 points (100.0% liked)

Lemmy Support

4733 readers
4 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
 

Edit: the issue was cloudflare proxy. If you're using cloudflare for dns, turn off proxying if you're using lets encrypt.

I must be doing something wrong, because when i run the playbook I get an unconfigured nginx page at the ip of my server.

The instruction docs for ansible states:

Do not edit anything inside the {{ }} braces.

https://github.com/LemmyNet/lemmy-ansible/blob/main/examples/config.hjson

however that config file points to:

https://join-lemmy.org/docs/administration/configuration.html

top 4 comments
sorted by: hot top controversial new old
[–] LastoftheDinosaurs@walledgarden.xyz 4 points 2 weeks ago (2 children)

vars.yml is looking for a directory and file that don't exist, and the readme doesn't mention creating them. If you set postgres_password manually, it should work.

[–] PriorityMotif@lemmy.world 3 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Thank you for the answer. should the password be in quotes?

postgres_password: "{{ lookup('password', 'inventory/host_vars/{{ domain }}/passwords/postgres.psk chars=ascii_letters,digits') }}" # noqa yaml[line-length]

postgres_password: "password"

[–] asudox@lemmy.asudox.dev 2 points 1 week ago

I'd say prefer single quotes for passwords as your password might have some special characters. Single quotes are raw strings, so nothing is escaped.

[–] PriorityMotif@lemmy.world 1 points 1 week ago* (last edited 1 week ago)

i'm still having issues I'm afraid. I do have a password in my local inventory/host_vars/{{ domain }}/passwords/postgres.psk and it does pass through to both POSTGRES_PASSWORD and PICTRS__SERVER__API_KEY in docker - compose.yml on the server.

docker compose logs show:

lemmy-1  | Error: LemmyError { message: Unknown("Error connecting to database"), inner: Error connecting to database
lemmy-1  | 
lemmy-1  | Caused by:
lemmy-1  |     connection to server at "postgres" (172.18.0.2), port 5432 failed: Connection refused
lemmy-1  |     	Is the server running on that host and accepting TCP/IP connections?
lemmy-1  |     , context: SpanTrace [] }
lemmy-1  | Lemmy v0.19.8
lemmy-1  | Error: LemmyError { message: Unknown("Error connecting to database"), inner: Error connecting to database
lemmy-1  | 
lemmy-1  | Caused by:
lemmy-1  |     connection to server at "postgres" (172.18.0.2), port 5432 failed: Connection refused
lemmy-1  |     	Is the server running on that host and accepting TCP/IP connections?
lemmy-1  |     , context: SpanTrace [] }
lemmy-1  | Lemmy v0.19.8
lemmy-1  | Error: LemmyError { message: Unknown("Error connecting to database"), inner: Error connecting to database
lemmy-1  | 
lemmy-1  | Caused by:
lemmy-1  |     connection to server at "postgres" (172.18.0.2), port 5432 failed: Connection refused
lemmy-1  |     	Is the server running on that host and accepting TCP/IP connections?
lemmy-1  |     , context: SpanTrace [] }
lemmy-1  | Lemmy v0.19.8
lemmy-1  | Error: LemmyError { message: Unknown("Error connecting to database"), inner: Error connecting to database
lemmy-1  | 
lemmy-1  | Caused by:
lemmy-1  |     connection to server at "postgres" (172.18.0.2), port 5432 failed: Connection refused
lemmy-1  |     	Is the server running on that host and accepting TCP/IP connections?
lemmy-1  |     , context: SpanTrace [] }
lemmy-1  | Lemmy v0.19.8
lemmy-1  | Error: LemmyError { message: Unknown("Error connecting to database"), inner: Error connecting to database
lemmy-1  | 
lemmy-1  | Caused by:
lemmy-1  |     connection to server at "postgres" (172.18.0.2), port 5432 failed: Connection refused
lemmy-1  |     	Is the server running on that host and accepting TCP/IP connections?
lemmy-1  |     , context: SpanTrace [] }
lemmy-1  | Lemmy v0.19.8
lemmy-1  | Federation enabled, host is dullsters.net
lemmy-1  | Starting HTTP server at 0.0.0.0:8536