Closed Teonyr closed 2 months ago
Teonyr
commented
2 months ago Okay, I found the issue:
In my docker-compose.yml I set the environment variable "FIREFLY_URL" for the pico container to http://firefly-app.
As it turns out, pico then tries to connect to firefly-app:80, but since firefly uses port 8080, this doesn't succeed.
Setting the port manually to 8080 fixes the issue:
- FIREFLY_URL=firefly-app:8080
Cloufish
commented
2 months ago I have very similar issue
I run the app behind traefik, but that shouldn't be the reason. I already had fireflyiii installed
My config:
version: "3.5"
services:
fireflypico:
image: cioraneanu/firefly-pico:latest
container_name: fireflypico
ports:
- "80"
networks:
- web
- fireflypico
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Warsaw
- FIREFLY_URL=https://fireflyiii.home
- DB_CONNECTION=pgsql
- DB_HOST=fireflypico_db
- DB_PORT=5432
- DB_DATABASE=firefly-pico
- DB_USERNAME=firefly-pico
- DB_PASSWORD=[REDACTED - SAME AS POSTGRES_PASSWORD]
depends_on:
- fireflypico_db
deploy:
labels:
- "traefik.enable=true"
- "traefik.http.routers.fireflypico.rule=Host(`fireflypico.home`)"
- "traefik.http.services.fireflypico.loadbalancer.server.port=80"
- "traefik.docker.network=web"
- "io.portainer.accesscontrol.users=admin"
- "traefik.http.routers.fireflypico.tls=true"
fireflypico_db:
image: postgres:latest
container_name: fireflypico_db
environment:
- POSTGRES_DB=firefly-pico
- POSTGRES_USER=firefly-pico
- POSTGRES_PASSWORD=[REDACTED - SAME AS DB_PASSWORD]
volumes:
- /home/swarm/fireflypico/:/var/lib/postgresql/data
networks:
- fireflypico
networks:
fireflypico:
driver: overlay
attachable: true
name: fireflypico
web:
external: true
name: web
volumes:
fireflypico-volume:
driver: localPostgreSQL Database directory appears to contain a database; Skipping initialization
2024-05-07 10:11:30.538 UTC [1] LOG: starting PostgreSQL 16.2 (Debian 16.2-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-05-07 10:11:30.539 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-05-07 10:11:30.539 UTC [1] LOG: listening on IPv6 address "::", port 5432
2024-05-07 10:11:30.543 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-05-07 10:11:30.549 UTC [29] LOG: database system was interrupted; last known up at 2024-05-07 10:11:25 UTC
2024-05-07 10:11:30.615 UTC [29] LOG: database system was not properly shut down; automatic recovery in progress
2024-05-07 10:11:30.617 UTC [29] LOG: invalid record length at 0/19DAB38: expected at least 24, got 0
2024-05-07 10:11:30.617 UTC [29] LOG: redo is not required
2024-05-07 10:11:30.623 UTC [27] LOG: checkpoint starting: end-of-recovery immediate wait
2024-05-07 10:11:30.636 UTC [27] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.005 s, sync=0.003 s, total=0.016 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=0 kB; lsn=0/19DAB38, redo lsn=0/19DAB38
2024-05-07 10:11:30.640 UTC [1] LOG: database system is ready to accept connections
2024-05-07 10:16:30.713 UTC [27] LOG: checkpoint starting: time
2024-05-07 10:16:30.928 UTC [27] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.201 s, sync=0.005 s, total=0.216 s; sync files=2, longest=0.005 s, average=0.003 s; distance=2 kB, estimate=2 kB; lsn=0/19DB438, redo lsn=0/19DB400Please help
cioraneanu
commented
2 months ago In the screenshot don't put any trailing "/" in the Pico backend URL.
If that's not it, you need to make sure that from your Pico container you can actually reach the Firefly API.
Ex. curl --location 'https://firefly.example.com/api/v1/about/user' --header 'authorization: Bearer xxxx' (replace firefly.example.com with your Firefly URL and xxxx with your personal token).
Issue
Hey, I'm trying to get pico up and running. Since I already have a firefly instance on docker, I used the
docker-compose.pico.ymlas a start.But when entering my access token, I receive "The provided endpoint + token is not correct."
No matter what I enter there, it always shows the same error.
docker-compose.yml
(Only the pico - part)
Log
I would appreciate any help and happily provide additional info if you need it.
Thanks. :)