TOTP K.O

[kimllee]

Description

Hi,

Looks like totp doesn't work or maybe the application I use on my phone is the issue.
I add the base32 secret generated on Trilium in the FreeOTP app to get a code but I can"t log in.
I use FreeOTP 2.3.5 for other apps and it works fine.

WARNING: Wrong totp from <ip>, rejecting.

Thank you.

TriliumNext Version

0.99

What operating system are you using?

Other (specify below)

What is your setup?

Local (no sync)

Operating System Version

Debian

Error logs

No response

[dosubot]

Hi @kimllee! I'm Dosu and I’m helping the Trilium team.

The most common causes for TOTP rejection in TriliumNext are time drift between your server and phone, incorrect entry or formatting of the base32 secret, or a mismatch in TOTP settings (digits, algorithm, time window) between Trilium and FreeOTP. Trilium expects a 16-character base32 secret, 6-digit codes, SHA-1, and a 30-second window—these are all standard and should work with FreeOTP, but double-check that FreeOTP is set to 6 digits and SHA-1 for this entry.

Make sure both your server and phone have the correct time (ideally synced via NTP); even a small drift can cause TOTP to fail. Also, confirm that you entered the secret exactly as shown, with no extra spaces or missing characters. If you use a reverse proxy, ensure it’s not interfering with headers or time.

There are no known compatibility issues between TriliumNext 0.99 and FreeOTP, and no special configuration is needed for FreeOTP. If you recently updated Trilium, note that a recent fix improved TOTP verification for some login flows, so updating to the latest version may help if you’re not already on it. More details: TOTP implementation and troubleshooting.

If you’ve checked all of the above and it’s still not working, try generating a new TOTP secret in Trilium and re-adding it to FreeOTP, watching for any typos or formatting issues.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}