search

ubergeek77 / Lemmy-Easy-Deploy

Deploy Lemmy the easy way!
MIT License
133 stars 14 forks source link

502 error in browser logs when doing first time login #86

Closed 3nderall closed 7 months ago

3nderall commented 7 months ago

Did you check the FAQ & Troubleshooting section for answers to common questions and issues?

Yes

Describe the issue

Can't login to my lemmy instance, it's an error with caddy not being able to reach the database to access login information. It is a new instance that I have just deployed. My browser logs say the error is 502. I have DISABLE_CADDY_TLS set to true because it was the only way I could find to make it work through nginx.

Diagnostic Information

Run ./deploy.sh -d and paste the output below:


==== Docker Information ====
Detected runtime: docker (Docker version 25.0.0, build e758fe5)
Detected compose: docker compose (Docker Compose version v2.24.1)
Runtime state: OK

==== System Information ==== OS: Linux KERNEL: 6.1.0-rpi7-rpi-v8 (aarch64) HOSTNAME: OK SHELL: bash MEMORY: total used free shared buff/cache available Mem: 7.8Gi 735Mi 110Mi 57Mi 7.1Gi 7.0Gi Swap: 99Mi 0B 99Mi

DISTRO:

PRETTY_NAME="Raspbian GNU/Linux 12 (bookworm)" NAME="Raspbian GNU/Linux" VERSION_CODENAME=bookworm

==== Lemmy-Easy-Deploy Information ==== Version: 1.3.3

IMAGE CREATED STATUS caddy:latest 16 minutes ago Up 15 minutes ghcr.io/ubergeek77/lemmy-ui:0.19.3 16 minutes ago Up 15 minutes (healthy) ghcr.io/ubergeek77/lemmy:0.19.3 16 minutes ago Up 15 minutes postgres:15-alpine 16 minutes ago Up 16 minutes asonix/pictrs:0.4.7 16 minutes ago Up 16 minutes

Integrity: 2cd5fe103e2d1d703edd5b2368a302e2aa56f005044b5aa182dfcb50e4803b02 deploy.sh 92c95dfc886792b8df2e9fffb540fc71a35c3bc6fd6c7662134da1545a79457a ./templates/Caddy-Dockerfile.template c1202e70662dd2228da36a35a0f38ec8fc81bec8964d7315d02e8671a58dd7d7 ./templates/Caddyfile.template 2537678c7971df36c1ed95f4228d3cfcb15bb4a28a60d939eaf8dd75b5d64a36 ./templates/cloudflare.snip c494a610bcb4cd1cfc0a4fe4fb0f6d437b2a84a0ad1625daee240e6dd6f1c910 ./templates/compose-email-volumes.snip c9cb4c5fee12930e17798a02ae1bd12e2dc69e149a394c24511bc9d4e6b776d4 ./templates/compose-email.snip 09b990908d667411c9089b6848cf63d30ad3e76b1e560747833c3cc241ab95a4 ./templates/docker-compose.yml.template 1c202b1b6e87c65b2fcda6035c9fe3f8631d76662907ffd38f24b14686e30647 ./templates/lemmy-email.snip c834cdce9eaf77f38155b404724fdfe66845575386ee516987452aa715642a6f ./templates/lemmy.hjson.template

Custom Files: No custom files

==== Settings ==== CLOUDFLARE: Yes CADDY_DISABLE_TLS: true CADDY_HTTP_PORT: 7061 CADDY_HTTPS_PORT: 7060 LEMMY_TLS_ENABLED: true ENABLE_EMAIL: false SMTP_PORT: 25 ENABLE_POSTFIX: false POSTGRES_POOL_SIZE: 5

==== Generated Files ==== Deploy Version: 0.19.3;0.19.3

total 40K drwxr-xr-x 2 0 0 4.0K Jan 22 16:12 caddy -rw-r--r-- 1 0 0 35 Jan 22 16:12 caddy.env -rw-r--r-- 1 0 0 1.7K Jan 22 16:12 docker-compose.yml drwxr-xr-x 2 0 0 4.0K Jan 22 16:12 lemmy-ui-themes -rw-r--r-- 1 0 0 50 Jan 22 16:12 lemmy.env -rw-r--r-- 1 0 0 469 Jan 22 16:12 lemmy.hjson -rw-r--r-- 1 0 0 49 Jan 22 16:12 pictrs.env -rw-r--r-- 1 0 0 39 Jan 22 16:12 postfix.env -rw-r--r-- 1 0 0 51 Jan 22 16:12 postgres.env -rw-r--r-- 1 0 0 14 Jan 22 16:12 version

3nderall commented 7 months ago

Also, the docker logs say it is a timeout on the proxy

3nderall commented 7 months ago

deleted the volumes and ./live and ran ./deploy.sh -f and it was fixed