Miniflux->Shaarli "Save" integration fails silently

Pioneer 25.12 behind router.

I’ve been using Miniflux and Shaarli for couple weeks now. I enabled the integration between the two webapps in Miniflux as documented here. To the best of my knowledge, selecting “Save” on a miniflux entry has produced an entry in Shaarli as expected.

Today, I experienced a condition that resulted in the miniflux entry NOT being saved in Shaarli, with no error indication in Miniflux… i.e., the “Save” option transitioned to “Done!” as it has done when I’ve successfully "Save"d other links.

In running sudo journalctl -f, the following error appears when engaging miniflux “Save”:

Oct 03 11:35:29 freebird miniflux[1300]: level=ERROR msg="Unable to send entry to Shaarli" user_id=1 entry_id=6330 ent
ry_url=https://www.bbc.com/future/article/20250926-why-england-forgot-its-first-king error="shaarli: unable to send re
quest: Post \"https://example.com/shaarli/api/v1/links\": dial tcp: lookup example.com: no such host"

ping6 example.com returns ping6: example.com: No address associated with hostname

So there are two problems here:

  1. Miniflux doesn’t indicate a problem with the “Save”.
  2. the fbx fails hostname resolution to itself?

Presumably, resolution was working fine as of 10:30pm last night, as that’s the last entry I saved before my attempt this morning.

the /etc/hostname file has the proper host machine name (although this isn’t references in any of the links I see, just the domain name), and the domain name is listed correctly in plinth System->Name Services.

Any suggestions?

rickbol

This issue has persisted after a reboot. There was the following journal entry after reboot, but before I tried to “Save” a miniflux entry:

Oct 03 12:36:46 freebird systemd[1]: systemd-hostnamed.service: Deactivated successfully.

Not sure if this is relevant or not.

Using a Firefox extension from my browser to save the current webpage URL to Shaarli (from my laptop) successfully saves the link in Shaarli on the fbx.

So this miniflux\shaarli problem appears limited to those apps running on the same fbx machine.