01-13-2021, 02:09 AM | #1 |
Connoisseur
Posts: 85
Karma: 449542
Join Date: Oct 2018
Device: Kobo Libra 2
|
KO reader Calibre wireless cannot connect
I'm using Version 2020.12-108 I just updated my ereader tonight, but it's been weeks since I've been able to get my Calibre wireless connection working, it used to work flawlessly until recently.
I get the message "Cannot connect to calibre server" Are there any ports I should be forwarding to make it work on my router? Nothing has really changed on my side of things. I'm wondering why this excellent feature seemingly randomly stopped working for me. I appreciate any help. I go to Calibre and select "Start wireless device connection" leave everything blank and then click OK then go to my "new:Calibre wireless connection" and then Connect" This method worked for almost a year, now suddenly with recent update it's stopped working. I tried automatic and manual with a ip and a port number, and it still doesn't work. Last edited by jasius; 01-13-2021 at 02:18 AM. |
01-13-2021, 12:03 PM | #2 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
(This is unlikely to be Kobo-specific, we have a dedicated KOReader forum. Or, better, GitHub).
That said, I can't really tell you much without logs. (c.f., opening a new GitHub issue for all the gory details). EDIT: Meh. There's not really much logging going on in the Calibre plugin on that front :/. So, generic obvious questions: is the Calibre instance running on the same network as your device, and is that network sane or heavily filtered or something? Try entering the actual IP/port manually instead of relying on auto discovery in KOReader, as some networks may make that unreliable. Last edited by NiLuJe; 01-13-2021 at 12:08 PM. |
01-13-2021, 02:46 PM | #3 | |
cosiñeiro
Posts: 1,271
Karma: 2200049
Join Date: Apr 2014
Device: BQ Cervantes 4
|
Quote:
About network topology: ip/port works always (as long as you can ping the ip of the calibre server from your kobo). Auto-discovery relies on your router, as it needs to broadcast the connection attempt to all the devices on your network. Auto-discovery can be flaky if you use some sort of wifi extender, different subnets or certain firewall rules. |
|
01-15-2021, 02:11 AM | #4 | |
Connoisseur
Posts: 85
Karma: 449542
Join Date: Oct 2018
Device: Kobo Libra 2
|
Quote:
I have recently added a wifi extender, so I tried to connect to my main router wirelessly and that didn't resolve the issue. I have both plugins\calibre.koplugin contains: (all .lua) _meta extensions main metadata search wireless plugins\calibrecompanion.koplugin contains: (all .lua) _meta main I appreciate your help, I hope we can get to the bottom of this one. As for my firewalls, all are pretty lax, but I'm asking which ports I need to open in case adding them manually will work. As I stated, I've given my wireless an IP and tried to manually enter said IP in my kobo reader and that hasn't worked. |
|
01-15-2021, 05:31 AM | #5 |
cosiñeiro
Posts: 1,271
Karma: 2200049
Join Date: Apr 2014
Device: BQ Cervantes 4
|
Ah, that explains the "new" in the name. You can remove "plugins\calibrecompanion.koplugin" if you wish. I will mark is as obsolete, to disable it from menus even when it is there.
About the network: port forwarding is something you do between your public IP and some IP behind the NAT. Is not applicable here. Even with a wifi extender you should be able to ping the computer that runs calibre from everywhere in your local network, including your kobo. You can test if you're able to ping from your kobo using the terminal plugin and typing Code:
ping -c1 ip_of_calibre If you're not able to ping the computer from your Kobo the calibre plugin won't work. |
01-18-2021, 12:44 AM | #6 | |
Connoisseur
Posts: 85
Karma: 449542
Join Date: Oct 2018
Device: Kobo Libra 2
|
Quote:
The Ping command came back with 13ms. I tried MANUAL but it still won't connect to Calibre, if this never worked ever I'd just shrug it off as an oddball feature, but the fact that it did at one point work is what's odd to me. |
|
01-18-2021, 08:04 AM | #7 | |
cosiñeiro
Posts: 1,271
Karma: 2200049
Join Date: Apr 2014
Device: BQ Cervantes 4
|
Quote:
Please double check that you're pinging the IP of calibre and you setup both the ip and the port that calibre uses. In the attachment you'll see my setup. Only one of the IPs is reachable from LAN. That's 192.168.8.254 in my case. It is also a static IP, but your computer might be using a dynamic ip provided by your router. So always check your setup matches the one that calibre reports |
|
01-19-2021, 11:14 PM | #8 | |
Connoisseur
Posts: 85
Karma: 449542
Join Date: Oct 2018
Device: Kobo Libra 2
|
Quote:
Thank you for the info. I made sure that I was using the correct info with the PING and the Manual port, it still didn't work though. I might have to chalk this one up to a loss, unless there's something I can post here on my ereader that might shed some light, if so just tell me exactly where to find it on there and I'll upload it. |
|
01-20-2021, 12:06 AM | #9 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Assuming you have shell access to your device (barring that, that should work in KOReader's Terminal plugin), you might want to check if netcat can actually reach Calibre from your device.
e.g., nc 192.168.1.42 9090 If Calibre is actually setup properly and reachable from your device, it should answer fairly rapidly with something like Code:
831[9, {"serverProtocolVersion": 1, "validExtensions": ["lrf", "rar", "zip", "rtf", "lit", "txt", "txtz", "text", "htm", "xhtm", "html", "htmlz", "xhtml", "pdf", "pdb", "updb", "pdr", "prc", "mobi", "azw", "doc", "epub", "fb2", "fbz", "djv", "djvu", "lrx", "cbr", "cbz", "cbc", "oebzip", "rb", "imp", "odt", "chm", "tpz", "azw1", "pml", "pmlz", "mbp", "tan", "snb", "xps", "oxps", "azw4", "book", "zbf", "pobi", "docx", "docm", "md", "textile", "markdown", "ibook", "ibooks", "iba", "azw3", "ps", "kepub", "kfx", "kpf"], "passwordChallenge": "", "currentLibraryName": "Calibre", "currentLibraryUUID": "6fc7c08a-4a8f-4833-8acd-f0a47d3aa201", "pubdateFormat": "MMM yyyy", "timestampFormat": "dd MMM yyyy", "lastModifiedFormat": "dd MMM yyyy", "calibre_version": [5, 9, 0], "canSupportUpdateBooks": true, "canSupportLpathChanges": true}] The default port (9090) should also accurate, but might want to set it manually, just in case... If nothing's answered (and/or the command actually fails and returns an error code), the problem lies outside of KOReader. And/or you have deeper network shenanigans at play. Last edited by NiLuJe; 01-20-2021 at 12:12 AM. |
01-22-2021, 12:35 AM | #10 |
Connoisseur
Posts: 85
Karma: 449542
Join Date: Oct 2018
Device: Kobo Libra 2
|
Sorry, should that reply you pasted there show up on my Ereader or somewhere on Calibre? I just see "EXECUTING" on my screen when I press the button to execute.
How long does it take? |
01-22-2021, 11:19 AM | #11 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Pretty much instantly, if all is well. If it hangs, and you're *certain* you're using the right IP & port, then you indeed have deeper network issues on your hand that have nothing to do with either Calibre or KOReader.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kobo Wireless (N647) does not connect to Kobo desktop, wifi or calibre. | aloalo27 | Kobo Reader | 6 | 12-26-2020 09:00 PM |
CC is connected to Calibre by wireless - No Reader | WannaKeepReading | Calibre Companion | 4 | 02-23-2017 10:06 PM |
Connect Kobo Arc7 HD to Calibre as Wireless Device | minidad2 | Kobo Tablets | 0 | 05-02-2015 02:31 PM |
[Calibre Portable and CC] No Wireless Option to Connect to | nynaevelan | Devices | 4 | 10-15-2012 09:05 AM |
iLiad cannot connect to the net either wire,wireless (no encription) or wireless(with encr) | tely | iRex | 5 | 04-24-2010 09:27 PM |