coolify icon indicating copy to clipboard operation
coolify copied to clipboard
verified publisher icon coollabsio

[Bug]: Postiz app fails to load

Open mandar-karhade opened this issue 9 months ago • 6 comments

Error Message and Logs

No error message / log in on the front end

Steps to Reproduce

  1. Install coolify
  2. Create environment
  3. Select new service postiz
  4. After starting (use the dropdown link from the service general page)
  5. register (no prompt of being successful)
  6. Use the same email to register (fails with warning that email is being used -- good confirmation)
  7. Log in using the email and password .. Nothing happens. Page does not redirect to the app itself

Example Repository URL

No response

Coolify Version

v4.0.0-beta.397

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Coolify

Additional Information

Postiz integration is having issues such that, it does not load the dash (main page) after registration / login page.

mandar-karhade avatar Mar 22 '25 20:03 mandar-karhade

Same issue, did you find a fix for it?

Cristy94 avatar Apr 13 '25 17:04 Cristy94

Somebody found a way to run postiz?

TmNiklas avatar Jun 01 '25 21:06 TmNiklas

Nobody cares about that problem, no solution nor returning error message. I am sure about developer have no idea too what causes this bug

hakanaltayagyar avatar Jun 04 '25 17:06 hakanaltayagyar

In my case, self hosted coolify, all the services are showing healthy. But when visiting the url it redirects to /launches and just blank dead screen. Looking at the network it gets 404 error at /api/users/self. Couldn't figure it out why it fails since all the services are healthy.

Image

millisami avatar Jun 16 '25 08:06 millisami

@andrasbacsai

  • Issue: External requests to /api/* returned 404/503 because Traefik was routing directly to the Next.js server (port 4200) instead of the in-container Caddy (port 5000). As a result, the backend (Nest on 3000) was never reached.
  • Fix: Added Traefik labels to force routing through Caddy on port 5000 and bound the routers to the correct service and network.
    • Set service port: traefik.http.services.postiz.loadbalancer.server.port=5000
    • Bound routers to the service: traefik.http.routers.*-postiz.service=postiz
    • Declared the Docker network: traefik.docker.network=<coolify network>
  • Outcome: /api/* now hits Caddy → proxied to backend on 3000; registration and health endpoints return 200/expected responses instead of 404/503.

Apurv-Salunke avatar Oct 29 '25 20:10 Apurv-Salunke