Skip to content

Troubleshooting

This page focuses on the three most frequent issues first.
More cases can be continuously added to the issue collection table.

1. What to do when login fails?

Typical symptoms

  • Connect action fails, or API version probe fails.
  • Server URL opens fine in browser, but app login still fails.

Confirm these four key items first

  1. Use root server URL: for example https://your-memos.example.com, do not append /api/....
  2. Login mode matches credential: Password mode uses username + password; Token mode uses PAT.
  3. API version is correct: login page requires selecting server version (0.21.0~0.26.0).
  4. Network and certificates: check proxy, firewall, certificate, and system time.

Check by mode

Token mode

  • Values pasted as Bearer ... are supported; prefix and spaces are auto-cleaned.
  • 401 usually means invalid token or insufficient permission.
  • "Version probe failed" is commonly version-selection mismatch first.

Password mode

  • Username and password must not be empty.
  • If credentials are correct but still fails, check selected server version and network reachability first.
  • For 0.23.0, full probe is skipped to reduce login wait time (intentional implementation strategy).
  1. Refill fields by comparing with Install and First Connection.
  2. Switch API version to actual server version and retry.
  3. Switch network (Wi-Fi / cellular) and retry.
  4. If still failing, keep exact error text and add it to issue collection.

2. What if AI summary says "no notes to send"?

What it actually means

AI summary reads memos from local database, within selected time range and filter rules.
If filtering leaves no eligible content, this prompt appears.

Most common causes

  1. Time range is too narrow.
  2. Allow private notes is off, so PRIVATE notes are filtered.
  3. Memo body is empty (empty content is skipped).
  4. Data has not synced into local DB yet.

Step-by-step checks

  1. Expand range from 7 days to 30 days or custom longer.
  2. Enable Allow private notes and retry.
  3. Pull to refresh / run manual sync, then retry.
  4. Open several memos to confirm body content is not empty.
  5. Confirm AI settings include valid API Key and API URL.

3. Issue collection table (continuous updates)

For each issue, include at least:

  • Reproduction steps
  • Current versions (app + Memos server)
  • Exact error text
  • Whether it reproduces consistently