read status no longer updated

[dosch]

Both on my phone (A9 hisense) as on my Ereader (lenovo smart paper) any article I read stays unread on miniflux.

Also when I read articles, close the app and reopen Miniflutt, the articles are back to unread status.

[DocMarty84]

Hello,
Have you tried to enable debug logging on server side? There hasn't been any fundamental change both on the client and the server recently, so it should work.

[ariasuni]

I have the same issue with miniflux.app, on Android 14: read status is lost when refreshing or restarting the app.

[dosch]

Hello, Have you tried to enable debug logging on server side? There hasn't been any fundamental change both on the client and the server recently, so it should work.

I haven't tried this and I haven't got around to test it yet. I run mniflux on top of Yunohost and miniflux -debug is not understood by Yunohost.

Any other way to enable and read Miniflux logs?

[dosch]

Is there any moving on this front?

I checked again with some apps, and so far only Miniflutt gives me this issue.
I hope it can be fixed, because by all my standards, this app is by far the best Miniflux companion on my phone!

[DocMarty84]

Hello,
I really need extra logging since I can't reproduce the issue.
If you can run miniflux with DEBUG=1, you should see something like this in the logs:

Jun 14 08:14:07 <xxx> miniflux[1678757]: level=INFO msg="[API] User authenticated successfully with the API Token Authentication" authentication_successful=true client_ip=<xxx> user_agent="Dart/3.6 (dart:io)" username=<xxx>
Jun 14 08:14:07 <xxx> miniflux[1678757]: level=DEBUG msg="Incoming request" client_ip=<xxx> request.method=PUT request.uri=/v1/entries request.protocol=HTTP/1.0 request.execution_time=34.254353ms

The request.method=PUT request.uri=/v1/entries request is the one updating the status of the entry.
From the installation script, I assume you should set the DEBUG flag in $install_dir/miniflux/miniflux.conf (not sure what is $install_dir). The logs will be in /var/log/miniflux/miniflux.log.

[dosch]

sadly /var/log/miniflux/ is empty...

I found that Miniflux sends all the logs to stderr and let the operating system takes care of the logs. As I have Debian and thus systemd, I can watch the logs with journalctl, but somehow nothing shows up for Miniflux.

I set debug level to INFO; this should capture everything... no?

---

Edit: I changed the log file location in the conf from stderr to /var/log/miniflux/miniflux.log and now it is recording logs.

When I browse miniflux using the miniflut app, I only see this line:

time=2025-06-14T14:22:27.465+02:00 level=INFO msg="[API] User authenticated successfully with the API Token Authentication" authentication_successful=true client_ip=XXX.XXX.XXX.XXX user_agent="Dart/3.6 (dart:io)" username=admin

There are no other entries so far.
When I mark an article as (un)read or starred; there are no new lines in the log.

But when I browse using the Reeder app (using the fever protocol) these messages apear in the log:

time=2025-06-14T14:26:40.909+02:00 level=DEBUG msg="[Fever] Receiving mark=item call" user_id=1
time=2025-06-14T14:26:40.915+02:00 level=DEBUG msg="[Fever] Mark entry as read" user_id=1 entry_id=9319
time=2025-06-14T14:26:40.917+02:00 level=DEBUG msg="Incoming request" client_ip=xxx.xxx.xxx.xxx
request.method=POST request.uri=/fever/?api request.protocol=HTTP/1.0 request.execution_time=14.203968ms

[dosch]

@DocMarty84 is there anything else I can provide you with that might help resolve this issue?

[lpukatch]

Double check that your miniflux instance URL is https. I had this issue where things were loading but not marking read and it was due to my URL becoming http instead of https

[dosch]

Indeed the URL had become http. But changing that to https didn't solve the issue... sadly. Would have been nice if it had been that easy.

[lpukatch]

Does the mark all as read button give you an error popup with a 308?

[dosch]

I get 301: moved permanently

[dosch]

@lpukatch I stand corrected. I tried again. And now it works.

Indeed, it was https becoming http...
Checnging that back (and saving the change!) solved it

Wow. took me almost 9 months to solve this