The requested resource isn't a valid image.

[gogowitsch]

📜 Description

When I click on a planned LinkedIn post, the software says Application error: a client-side exception has occurred (see the browser console for more information)..

In the network tab, there is a failed request with the body The requested resource isn't a valid image.
The request URL is https://postiz.blaeul.de/_next/image?url=%2Ficons%2Fplatforms%2Fundefined.png&w=48&q=75
The HTTP status is 400 Bad Request.

The connected LinkedIn profile has the default picture:

👟 Reproduction steps

See above

👍 Expected behavior

The “edit post” modal should appear.

👎 Actual Behavior with Screenshots

Before:

After clicking:

💻 Operating system

Linux

🤖 Node Version

v20.17.0

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

Are you willing to submit PR?

None

[jamesread]

hmm, unusual.

Did you change STORAGE_PROVIDER?

Are you able to upload images with the Media Uploader?

Are you able to remove and re-add the LinkedIn provider?

If you switch to the "Console" view, are there any error messages there?

[gogowitsch]

Thanks for your quick response!

STORAGE_PROVIDER is the default "local". I am using Docker Compose with this environment:
MAIN_URL: "https://postiz.blaeul.de"
FRONTEND_URL: "https://postiz.blaeul.de"
NEXT_PUBLIC_BACKEND_URL: "https://postiz.blaeul.de/api"
JWT_SECRET: redacted
DATABASE_URL: redacted
REDIS_URL: redacted
BACKEND_INTERNAL_URL: "http://localhost:3000"
IS_GENERAL: "true"
STORAGE_PROVIDER: "local"
UPLOAD_DIRECTORY: "/uploads"
NEXT_PUBLIC_UPLOAD_DIRECTORY: "/uploads"
X_API_*
LINKEDIN_*
EMAIL_*

My docker-compose.yml is set to use this docker image: ghcr.io/gitroomhq/postiz-app:amd64-1732078462

Uploading and posting media works, even on LinkedIn.

Deleting and adding the LinkedIn provider works; it’s very easy. The error remains: clicking on a LinkedIn post in the calendar view triggers the error in the screenshot above. Clicking on a post of any other provider works.

The browser console shows 2 errors: