Klaus
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
I also noticed the log time is one hour out. Could that create any issues?
36 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
“The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.”
Does this need to be reflected in the compose file?
36 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
I had to change the postgres healthcheck to reflect the actual user name — sorry about that. But it still doesn’t work. Sending the postgres log below.
36 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
The one and only log entry for Postgres is
FATAL: role "postiz-user" does not exist
36 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
Hi all, thanks so much and apologies for not checking in earlier. I can now register a user (registering same email a second time returns “email already exists”). But the login still does not work, it simply returns back to the login page.
36 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
Thanks @zapoqx, this is slightly "above my paygrade", as they say. When the message suggests running a command to resolve the issue, did you find that to be the solution? If so, where/how would I need to run it? Thanks!
36 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
Hi @Support/@xcons, thanks so much for your initial help. I was hoping that providing more information might help resolve the issue -- I hope it wasn't counterproductive! 🙂
36 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
As an additional note: I changed to 5437:5432 because of a bind error. Could that error be related to using localhost in BACKEND_INTERNAL_URL: "http://localhost:3000/", in that localhost might refer back to the wrong service?
36 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
services:
postiz:
image: ghcr.io/gitroomhq/postiz-app:latest
container_name: postiz
restart: always
environment:
# You must change these. Replace
postiz.your-server.com with your DNS name - what your web browser sees.
MAIN_URL: "https://postiz.SERVER.COM"
FRONTEND_URL: "https://postiz.SERVER.COM"
NEXT_PUBLIC_BACKEND_URL: "https://postiz.SERVER.COM/api"
JWT_SECRET: "placeholder"
DATABASE_URL: "postgresql://XXX:YYY@postiz-postgres:5437/postiz-db-local"
REDIS_URL: "redis://postiz-redis:6379"
BACKEND_INTERNAL_URL: "http://localhost:3000"
IS_GENERAL: "true" # Required for self-hosting.
STORAGE_PROVIDER: "local"
UPLOAD_DIRECTORY: "/uploads"
NEXT_PUBLIC_UPLOAD_DIRECTORY: "/uploads"
volumes:
- /volume1/docker/postiz/config:/config/
- /volume1/docker/postiz/uploads:/uploads/
ports:
- 5000:5000
networks:
- postiz-network
depends_on:
postiz-postgres:
condition: service_healthy
postiz-redis:
condition: service_healthy
postiz-postgres:
image: postgres:14.5
container_name: postiz-postgres
restart: always
environment:
POSTGRES_PASSWORD: YYY
POSTGRES_USER: XXX
POSTGRES_DB: postiz-db-local
volumes:
- /volume1/docker/postiz/postgres:/var/lib/postgresql/data
ports:
- 5437:5432
networks:
- postiz-network
healthcheck:
test: pg_isready -U postiz-user -d postiz-db-local
interval: 10s
timeout: 3s
retries: 3
postiz-redis:
image: redis:7.2
container_name: postiz-redis
restart: always
ports:
- 6379:6379
healthcheck:
test: redis-cli ping
interval: 10s
timeout: 3s
retries: 3
volumes:
- /volume1/docker/postiz/data:/data
networks:
- postiz-network36 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
Below follows the composer file (adapted from the postiz docs):
36 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
Just discovered that I get an earlier error when running the docker compose file: [Nest] 130 - 10/23/2024, 8:38:57 AM ERROR [PrismaClientInitializationError: Can't reach database server at
postiz-postgres:5437
Please make sure your database server is running at postiz-postgres:5437.] Backend failed to start on port 300036 replies
PPostiz
•Created by Support on 10/21/2024 in #💭│community-support-tickets
HTTP 502 on Synology NAS with Docker/Reverse Proxy
Of course, apologies for not including them before. They all follow this pattern: ERR ts=1729516147.5200381 logger=http.log.error msg=dial tcp 127.0.0.1:3000: connect: connection refused request={"remote_ip":"192.168.208.1","remote_port":"46030","client_ip":"192.168.208.1","proto":"HTTP/1.1","method":"GET","host":"postiz.XXX","uri":"/api/auth/oauth/GOOGLE","headers":{"Pragma":["no-cache"],"Priority":["u=3, i"],"Connection":["close"],"Accept":["application/json"],"Accept-Language":["en-GB,en;q=0.9"],"User-Agent":["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0.1 Safari/605.1.15"],"Referer":["https://postiz.XXX/auth/login"],"Content-Type":["application/json"],"Sec-Fetch-Mode":["cors"],"Sec-Fetch-Dest":["empty"],"X-Forwarded-For":["172.225.6.72"],"Sec-Fetch-Site":["same-origin"],"Cache-Control":["no-cache"],"Accept-Encoding":["gzip, deflate, br"],"X-Real-Ip":["172.225.6.72"],"X-Forwarded-Proto":["https"]}} duration=0.000611542 status=502 err_id=0u5z6s66d err_trace=reverseproxy.statusError (reverseproxy.go:1267)
36 replies