After railway up in my postgres database the problem is that the server did not conect to my n8n at all

Hi there - this looks like an issue with the n8n setup itself. Looking to our community to help here

The “public user does not exist” message means n8n’s compulsory ​public​ account was deleted or never created.

Check the logs for the following:

insert into "user_entity"

("id","email","firstName","lastName","globalRoleId","password","createdAt","updatedAt")

values

('public','public@n8n.io','Public','User',

(select id from "role_entity" where name = 'member' limit 1),

'', now(), now())

on conflict ("id") do nothing;

Guys, I have fixed the problem, however today after automatically move to metal my postgres base it crashed again with the same error. Railway team please help me and stop upgrading to metal. Crashed my base 2 times

Guys, I have fixed the problem, however today after automatically move to metal my postgres base it crashed again with the same error. Railway team please help me and stop upgrading to metal. Crashed my base 2 times

How did you fix it the first time? Curious

I have rollback the server from metal edge to my legacy server . Also i have reconfigured through CLI forcing the n8n app to update tables