Deployment issue on Railway
I'm experiencing an issue with my Wasp app deployment that started after the recent Railway update (April 4 changelog).
My app was working fine before, but now deployments are failing with this error:
pg-boss failed to start!
error: role "u9o4bahro8glkv" is not permitted to log in
The strange thing is, when I check my database using \du and SELECT rolname, rolcanlogin FROM pg_roles;, this role doesn't exist in my database at all. The only role with login privileges is "postgres", which matches my DATABASE_URL connection string (postgresql://postgres:PASSWORD@nozomi.proxy.rlwy.net:XXXX/railway).
This suggests something at the Railway infrastructure level is trying to use a different username than what's in my connection string. I haven't made any changes to my database configuration, and this was working before the recent update.
I suspect this is a Railway issue, unrelated to Wasp, but just wanted to ask - Has anyone else experienced similar issues with pg-boss or database connections on Railway after the update? Any guidance on how to resolve this would be greatly appreciated.
I'm on V0.15 of Wasp.
My app was working fine before, but now deployments are failing with this error:
pg-boss failed to start!
error: role "u9o4bahro8glkv" is not permitted to log in
The strange thing is, when I check my database using \du and SELECT rolname, rolcanlogin FROM pg_roles;, this role doesn't exist in my database at all. The only role with login privileges is "postgres", which matches my DATABASE_URL connection string (postgresql://postgres:PASSWORD@nozomi.proxy.rlwy.net:XXXX/railway).
This suggests something at the Railway infrastructure level is trying to use a different username than what's in my connection string. I haven't made any changes to my database configuration, and this was working before the recent update.
I suspect this is a Railway issue, unrelated to Wasp, but just wanted to ask - Has anyone else experienced similar issues with pg-boss or database connections on Railway after the update? Any guidance on how to resolve this would be greatly appreciated.
I'm on V0.15 of Wasp.
