My Postiz app at https://postiz-production-a911.up.railway.app won’t let me log in (it reloads the login page forever). Please fix the service so the app runs correctly on your platform.

• Make sure the container’s default start command is used (no Next.js custom start).

• Ensure the public domain maps to the container’s listening port.

• Confirm the app’s internal API is reachable so auth works.
  Here are the variables I’ve set:

FRONTEND_URL=https://postiz-production-a911.up.railway.app
NEXT_PUBLIC_BACKEND_URL=https://postiz-production-a911.up.railway.app/api
BACKEND_INTERNAL_URL=<<<Railway, set this to whatever your platform requires so the app can call itself internally>>>
JWT_SECRET=*** set ***

Please adjust the target/internal port and start command as needed for the official image ghcr.io/gitroomhq/postiz-app so login stops looping.

2) Message to Postiz Support

I’m deploying the official image ghcr.io/gitroomhq/postiz-app on Railway at https://postiz-production-a911.up.railway.app. I can open the login page but after entering credentials it just refreshes back to login.
Env I set:

FRONTEND_URL=https://postiz-production-a911.up.railway.app
NEXT_PUBLIC_BACKEND_URL=https://postiz-production-a911.up.railway.app/api
BACKEND_INTERNAL_URL=*** (Railway’s correct internal URL/port for this image) ***
JWT_SECRET=*** set ***

Can you confirm the required env vars and the expected listening port for this image on PaaS (Railway)? Also confirm whether any auth-related cookie/domain settings are required for single-URL deployments.