Local Storage Forced, Image Cache Fails

[davidbrrrr]

Hi all,

I’m running into a consistent issue with the Postiz app on Cloudron.

Even when simply loading the Postiz UI (e.g. /launches, /media, /agents, /settings), I get repeated errors like:

Failed to write image to cache ... mkdir '/app/code/apps/frontend/.next/cache/images'
ENOENT: no such file or directory

Cloudron mounts /app/code as read‑only, so the Next.js image optimizer cannot create this directory. This happens on every page load, not only during integrations.

When trying to add a LinkedIn Page, the OAuth flow completes, but the final step fails with:

LocalStorage.uploadSimple
Request failed with status code 403

It seems Postiz tries to upload the LinkedIn avatar/logo via the local upload endpoint, but the Cloudron package forces:

STORAGE_PROVIDER=local

in start.sh, so external storage (S3/R2) cannot be used even if configured in /app/data/env.

As a result:

• Next.js cannot write cached images (read‑only filesystem)
• LocalStorage uploads fail with 403
• Adding channels like LinkedIn Page becomes impossible

Am i on the right track here? Can someone else confirm what i described? What are workarounds or possible solutions to this? I really would like to use postiz via cloudron.

Thanks!

David

[james]

Hello @davidbrrrr
The first issue you mentioned .next/cache is okay and can be ignored.

The following issue with 403 seems to be a known issue upstream with localStorage.

• https://github.com/gitroomhq/postiz-app/issues/972
  and
• https://github.com/gitroomhq/postiz-app/issues/918#issuecomment-3254171711
  and there even is a PR that fixes this issue: https://github.com/gitroomhq/postiz-app/pull/1085

This is an upstream issue and can't be fixed by Cloudron sadly.
The maintainers of Postiz need to add this fix.

[p.omar.s]

Hi everyone
I’m running Postiz on Cloudron and I’m trying to connect a LinkedIn company page, but I’m stuck.
The OAuth flow itself looks fine
I get redirected to LinkedIn, the login works, but after the redirect back to Postiz it fails with the message:

• Could not add provider. You are being redirected back.

Here’s what I’ve already checked:

• Postiz is running stable on Cloudron
• Persistent storage is set up correctly (/app/data)
• I restarted Postiz cleanly
• No crashes or startup errors show up in the logs
• The LinkedIn redirect URLs are configured correctly
• The LinkedIn company page is linked and verified in the LinkedIn app
• Organization-related OAuth scopes are visible in the app

Enabled LinkedIn products are currently:

• Share on LinkedIn (Default Tier)
• Sign In with LinkedIn using OpenID Connect
• Advertising API (Development Tier)

Has anyone run into a similar issue when connecting LinkedIn company pages to Postiz on Cloudron, or knows what else I should check to get this working?
Any help or pointers would be really appreciated.
Thanks

[james]

Hello @p.omar.s and welcome to the Cloudron community forum

What you are describing is the same issue as stated above with the same conclusion as above.
This unfortunately is a @postiz issue that could only be resolved by us applying a custom patch.

Adding to that from the Postiz Discord I could gather that "Nevo David" the maintainer of @postiz is currently working on a bigger change from BullMQ to Temporal.
This could explain why many PRs are still awaiting merging.