Spaces:

---

Duplicated from  EnzGamers/n8n-free

baoyin2024

/

n8n-free

like 151

Running

Hi, according to my understanding, you should've pointed the DB to your own one hosted elsewhere upon duplicating this instance. If you have not done that (changing the env. variables at configuration when duplicating it), your instance is likely pointing to baoyin2024's original DB, which he'll likely not telling you his/her credentials. =)

Modified the configuration, and the database also saw the user's email

N8N_ENCRYPTION_KEY
N8N_ENCRYPTION-KEY, I have defined my own password

Problem logging in
Wrong username or password. Do you have caps lock on?

did you insert those 2 user accounts manually within supabase? is this the 1st time login (which should've asked for admin account creation)?

did you insert those 2 user accounts manually within supabase? is this the 1st time login (which should've asked for admin account creation)?

This is indeed my first login.
Need to add login email and password to the database and user table.

-- 必须用双引号包裹表名"user"
INSERT INTO "user" (
    email, 
    password, 
    first_name, 
    last_name, 
    personalization_answers,
    global_role_id,
    created_at, 
    updated_at
) VALUES (
    '[email protected]', 
    crypt('password123', gen_salt('bf')),  -- 密码加密
    'John', 
    'Doe', 
    '{"survey": {}}'::jsonb,
    '1',  -- 全局角色ID（1通常是所有者）
    NOW(), 
    NOW()
) RETURNING *;

Presumably, you've tried login with the user name ([email protected] or whatever you've set) and pass (password123 or whatever you've set) which lead to a login failure?

Then, let's see what we've done differently. While I was duplicating the instance, I've also setup my DB with Supabase. I didn't however provision the user account with such manual query. Instead, I merely opened n8n instance and followed its initial admin account setup form. After which, I'm able to login as anticipated. It has been working as a charm ever since. That said, perhaps you can try it this way. In case it works out, you can then safely tell that the issue occurs at the manual DB query script you have mentioned above. If you wanna pinpointing exactly where the script has gone south, maybe this needs to be compared with n8n's official doc.

btw, I'm not entirely sure what's n8n's logic in triggering the initial admin account setup form. If it merely checks whether user table is empty or not, then you can just drop the entries you've created in the user table and restart n8n instance to let it check & run again, which may trigger the initial account setup again. Or otherwise, as you cannot even login from the beginning, i assume there's nothing have been created within your current DB. Then the easiest could've been just recreate the DB and modify the env. variables on n8n to re-point to the new DB instance. however you wanna approach it.

把Supabase删除，再重建重新部署，第一次登录n8n后设置，别忘记了，以前我也碰到过

把Supabase删除，再重建重新部署，第一次登录n8n后设置，别忘记了，以前我也碰到过

好的，谢谢，你这个很好。 我通过修改数据库 user表，通过sql命令插入用户解决了。

在数据库插入命令用的就是这个。对应的修改成自己用户名 和 密码就可以

- 必须用双引号包裹表名"user"
INSERT INTO "user" (
    email, 
    password, 
    first_name, 
    last_name, 
    personalization_answers,
    global_role_id,
    created_at, 
    updated_at
) VALUES (
    '[email protected]', 
    crypt('password123', gen_salt('bf')),  -- 密码加密
    'John', 
    'Doe', 
    '{"survey": {}}'::jsonb,
    '1',  -- 全局角色ID（1通常是所有者）
    NOW(), 
    NOW()
) RETURNING *;