Ticket: Error: Posting Images to X - getaddrinfo enotfound
@m4rk Just created a ticket
Question: Cant make post with images to X. ERROR getaddrinfo enotfound postiz.xxx.xxx
Attempted: change image type , format and check out permissons .
Working On: Trying to post images to X and instagram.
Using Postiz On: Docker Compose
Take it from here @Postiz
Question: Cant make post with images to X. ERROR getaddrinfo enotfound postiz.xxx.xxx
Attempted: change image type , format and check out permissons .
Working On: Trying to post images to X and instagram.
Using Postiz On: Docker Compose
Take it from here @Postiz
26 Replies
Ill leave the logs in here in case this helps
It seems this remains true for discord and all other apps:
Wondering if this was an installation issue or permissions issue
Reinstalled on a new machine..
Totally new... It gives same errors
Any advice now will be greatly appreciated
@Support do you think I can get help ?
@Postiz please help @m4rk
In case it helps.
I tried installing on VM/ware machine and bare metal server using the following tutorial:
https://www.alanbonnici.com/2024/12/howto-self-host-postiz-on-ubuntu-on.html
HowTo Self Host Postiz on Ubuntu (on Proxmox VE)
This blog is about security and computing related topics with occassional hobby activities thrown in.
This is whay I get if trying to post an image
This is my docker-compose.yml
@Postiz please help @m4rk
any tips will be greatly appreciated
I think I got the same issues not only with X, but with all socials
Tested this on ubuntu vm instead of synology containers, and getting the same issue - not sure if we are missing something or there's an issue with the application
@Postiz please help @m4rk
Are you using Caddy as reverse proxy as well?
I used Caddy on the ubuntu, on synology I use the standard reverse proxy that comes with it
I can't get R2 to working at all to even test it
hope support can help us get a clue on what we are doing wrong
Suppor team this might be a bug , please let us know if we are missing something
@Matt would you share your docker-compose.yml file ??
I am thinking on something that might be the issue but still needs testing
Did you try changing the ownership of the /upload directory?
Just for testing, i know you should not use it in production. Try chmod 777 on it just to check up
Havent tried
Shall I just go where the volume is and chmod /var/lib/docker/volumes/……/uploads directory ?
Yes
Kk let me try .. fingers crossed
nope didnt work 😦
ill try to maybe changeing the directory and bindind one from the host... might just work
I can't send the whole one because discord limits message lenghts -_-
That's my cloudfare test - this one doesn't work at all. I get storage errors when trying to post 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.f3.local"
FRONTEND_URL: "https://postiz.f3.local"
NEXT_PUBLIC_BACKEND_URL: "https://postiz.f3.local/api"
JWT_SECRET: "dnkhfhweqhkqw95812nkasdldas012nbasbjdasjwhkasdpowpaodsanmcasdxdtgkej"
# These defaults are probably fine, but if you change your user/password, update it in the
# postiz-postgres or postiz-redis services below.
DATABASE_URL: "postgresql://postiz-user:postiz-password@Postiz-postgres:5432/postiz-db-local"
REDIS_URL: "redis://postiz-redis:6379"
BACKEND_INTERNAL_URL: "http://localhost:3000"
IS_GENERAL: "true" # Required for self-hosting.
# The container images are pre-configured to use /uploads for file storage.
# You probably should not change this unless you have a really good reason!
CLOUDFLARE_ACCOUNT_ID: "xxx"
CLOUDFLARE_ACCESS_KEY: "xxx"
CLOUDFLARE_SECRET_ACCESS_KEY: "xxxx"
CLOUDFLARE_BUCKETNAME: "postiz"
CLOUDFLARE_BUCKET_URL: "https://xxxx.r2.dev/"
CLOUDFLARE_REGION: "WEUR"
volumes:
- postiz-config:/config/
- postiz-uploads:/uploads/
ports:
- 5000:5000
networks:
- postiz-network
depends_on:
postiz-postgres:
condition: service_healthy
postiz-redis:
condition: service_healthy
This one is for local storage and I can post but just images fail: 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.f3.local"
FRONTEND_URL: "https://postiz.f3.local"
NEXT_PUBLIC_BACKEND_URL: "https://postiz.f3.local/api"
JWT_SECRET: "dnkhfhweqhkqw95812nkasdldas012nbasbjdasjwhkasdpowpaodsanmcasdxdtgkej"
# These defaults are probably fine, but if you change your user/password, update it in the
# postiz-postgres or postiz-redis services below.
DATABASE_URL: "postgresql://postiz-user:postiz-password@Postiz-postgres:5432/postiz-db-local"
REDIS_URL: "redis://postiz-redis:6379"
BACKEND_INTERNAL_URL: "http://localhost:3000"
IS_GENERAL: "true" # Required for self-hosting.
# The container images are pre-configured to use /uploads for file storage.
# You probably should not change this unless you have a really good reason!
CLOUDFLARE_ACCOUNT_ID: "70577511ce1805d2b3cd16b763eb6088"
CLOUDFLARE_ACCESS_KEY: "aae68345c2ea4748ab24f7e028f1d8a3"
CLOUDFLARE_SECRET_ACCESS_KEY: "b9934770462065e7a64254a87bcbf443b6f961e910e648ac660959262da629da"
CLOUDFLARE_BUCKETNAME: "postiz"
CLOUDFLARE_BUCKET_URL: "https://pub-32e500d14cc3415f990e226d78bb1f1c.r2.dev/"
CLOUDFLARE_REGION: "WEUR"
STORAGE_PROVIDER: "local"
UPLOAD_DIRECTORY: "/uploads"
NEXT_PUBLIC_UPLOAD_DIRECTORY: "/uploads"
volumes:
- postiz-config:/config/
- postiz-uploads:/uploads/
@m4rk did you manage to get your one running using r2?Nope
Still checking along what can be wrong 😦
If i set STORAGE_PROVIDER: "cloudfare" i get error 502 everywhere now lol
@jamesread you think you can point us in right direction?
Let me know if any information is missing
This was solved using Cloudflare r2.