Boox issues with local network OPDS

https://sh.itjust.works/post/57587490

Boox issues with local network OPDS - sh.itjust.works

Question for those of you here. I recently purchased a used Boox Note Air 4C so that my son could read manga on a larger screen than the ancient kindle paperwhite we had previously. I’ve been running a Booklore library and using KOReader on the kindle so he can fetch the books down that he wants. The first thing I did when setting up the new Boox was to grab KOReader and point it to our local Booklore OPDS catalogue. For some reason the Boox cannot see the catalogue or any of the other services I have hosted on my network. All of my local services (including booklore) are behind a reverse proxy (NGINX) and use a certificate to move to https. The domain is registered but only works for me since it provides a local network ip when hit. Has anyone faced a similar problem with boox and identified a way around it? I suspect this is either (1) the Boox cannot interpret the local address correctly when it hits DNS for my domain or (2) its network configuration is somehow blocking it from ever accessing local network (seems odd).

Do you get any kind of error when adding the OPDS URL?

Just transferred booklore over to its new fork (grimmory), noting here due to the (small) environment change.

The error I receive on the Boox unit is “Cannot get catalog. Server response status: timeout.” I am still doing some additional troubleshooting. Note that other self-hosted services (e.g. Heimdall) are also not reachable from the Boox.

Just confirmed that both are running KOReader v2025.10.

Edit: I’m not sure what changed and/or I’m an idiot. I just changed which internal network I was connected to and it fixed the problem. Not sure how I overlooked this.
Was going to ask to check what the DNS server was for the boox, thinking that maybe you’re not connected to your WiFi at all.