Pocketbook fix

[mauamy]

Add code that allows to run filebrowser on pocketbook devices (tested on Pocketbook Era).

I basically took kaporjan's code from https://github.com/b-/filebrowser.koplugin/issues/2 and combined it with the current code and ffi/util.isPocketbook().

[tawar-ger]

I use a pocketbook Inkpad Color 3. What exactly do I have to change so that the file browser runs for me? Is there perhaps a finished file to download?

[mauamy]

@tawar-ger Yes, you can test my fix by installing filebrowser like described in the README and then downloading the main.lua from my fork/branch and replace the main.lua in your installed filebrowser.koplugin directory on your device with my main.lua. Afterwards restart koreader and check if you can start filebrowser (go to settings --> network (wifi must be enabled) --> tab on the filebrowser option).

I also changed the default port of filebrowser to 8080, so open a browser on any device in the same network as your reader and go to http://:8080

[tawar-ger]

@tawar-ger Yes, you can test my fix by installing filebrowser like described in the README and then downloading the main.lua from my fork/branch and replace the main.lua in your installed filebrowser.koplugin directory on your device with my main.lua. Afterwards restart koreader and check if you can start filebrowser (go to settings --> network (wifi must be enabled) --> tab on the filebrowser option).

I also changed the default port of filebrowser to 8080, so open a browser on any device in the same network as your reader and go to http://:8080

Thank you for your prompt response. It is finally working for me as well. This is so brilliant. I appreciate it.

[davidbaranek]

Hi, I have a PocketBook Verse Pro and even with your fix, it still doesn’t work. The checkbox is checked and there are no errors in crash.log or filebrowser.log, but I still can’t connect to the device (I get ERR_CONNECTION_TIMED_OUT).

filebrowser.log seems fine.”
2025/12/27 17:03:23 Listening on 0.0.0.0:8080
2025/12/27 17:05:05 Got signal: interrupt
2025/12/27 17:05:05 Stopped serving new connections.
2025/12/27 17:05:05 Graceful shutdown complete.

crash.log:
12/27/25-17:03:22 INFO [Filebrowser] Filebrowser started. Find Filebrowser logs at /mnt/ext1/applications/koreader/plugins/filebrowser.koplugin/filebrowser/filebrowser.log
2025/12/27 17:03:23 Using database: /mnt/ext1/applications/koreader/plugins/filebrowser.koplugin/filebrowser-new.db
2025/12/27 17:03:23 No config file used
12/27/25-17:03:27 INFO Inhibiting user input
[2199:27/12/25 17:03:51] netagent called with parameters < ping >
[2239:27/12/25 17:04:22] netagent called with parameters < ping >
[2254:27/12/25 17:04:52] netagent called with parameters < ping >

Do you have any idea, where is the problem? Thanks

[mauamy]

@davidbaranek Can you tell me what the network information in koreader shows (Cog Settings --> Network --> Network Info) and how you are trying to connect to the filebrowser?

[davidbaranek]

@davidbaranek Can you tell me what the network information in koreader shows (Cog Settings --> Network --> Network Info) and how you are trying to connect to the filebrowser?

Network information:

Interface: eth0
MAC: 88:6F:29:19:65:26
SSID: “iPhone 12 mini”
IP: 172.20.10.2
Default gateway: 172.20.10.1
Gateway ping: FAILED

I tried a couple of networks. I’m connecting from my computer or phone on the same Wi-Fi network to http://172.20.10.2:8080. I also tried http://0.0.0.0:8080 in the PocketBook’s built-in browser, but with no luck.

Maybe this is related to the SSH server also not working, but I don’t see the same error in the log.

[mauamy]

Did you also try a non hotspot network? iirc iphone hotspots are not designed like wifi-routers and you are not able to reach other devices within the hotspot network. Or can you access other devices within the hotspot network and only the pocketbook filebrowser is not working?

[davidbaranek]

I don’t know why, but it suddenly started working perfectly (both on my hotspot and my home Wi-Fi). Maybe it was some issue on my local network or PC, but that seems weird since it failed on both the hotspot and home Wi-Fi, on both my phone and my PC. Anyway, thank you very much for your help and this pr!