Jock Busuttil

Correction (my bad): I had installed using `npm install -g n8n` (not source as originally posted, bug report edited) n8n is launched from systemd: ``` [Unit] Description=n8n v1.16.0 server After=syslog.target...

Just to update on this, I disabled and re-enabled 2FA to regenerate the recovery codes, then I continued to log in using the authenticator app (again not using the recovery...

Hi @Joffcom - I've just upgraded to `1.20.0` - I'm assuming the 2FA issue is fixed as you've kindly highlighted, so I'll close this and reopen if not. Thanks!

@Joffcom Alas - still seeing the same problem in `1.20.0` - reopening. Notification that all 2FA recovery codes have been used now appears after

HNY @Joffcom EDIT version (because typo): I've tested with 1.21.1, but **not on a clean install.** Test 1: After enabling MFA, the notification pops up that all recovery codes have...

@Joffcom Sorry - typo in the version number, should have been 1.21.1 (current 'latest' using `n8n update` at time of writing). I've updated the earlier comment to avoid confusion. (It's...

@Joffcom Happy to, let me know what you need me to do 👍

Thanks @Joffcom - I have an uncanny knack of triggering obscure bugs, thanks for investigating

@RicardoE105 The problem became much less frequent in the stable versions released around late January / early February (2024), then went away almost entirely in subsequent stable releases. I think...

 Triggered again for first time in a while for me n8n self-host 1.42.1 Firefox 126.0.1 (64-bit, Windows 10)