KOReader server down? - Page 2

boox · 08-26-2023, 12:55 AM

ota.koresder.rocks is online again.

Frenzie · 08-26-2023, 12:42 PM

Quote:

Originally Posted by NiLuJe

I can't really mirror it (both because it's down so I can't really access the data, and also the official implementation is a right PITA to deploy on my end anyway), but I've spun up a different instance of a different KOSync implementation, at https://kosync.ak-team.com:3042 if you *really* need *a* sync server, for some reason.

There are various alternative sync server implementations btw. Given that none of us is particularly interested in the sync functionality (though of course it doesn't need to do much) it's easily possible they're all much better.

NiLuJe · 08-27-2023, 12:48 PM

I don't really have anything against Redis & Openresty, they (well, Openresty really) just happen to be slightly more invasive and involved to deploy than a standalone Rust or Go binary (or a Python web app) (especially if you can't/won't use Docker; and both apply here: I'd have to mangle my kernel & systemd configs to even be able to run Docker, while I can pretty much isolate a random binary in a much clearer fashion with a simple systemd unit).
And I'd have to mangle my already custom nginx & luajit ebuilds to just go native with OpenResty, as it isn't packaged in the main Portage tree. And, again, nginx configs.

(And, also, running a whole OS layer in a container, even a slim one, just to run a 5MB daemon doesn't really jive well with me ;p).

Frenzie · 08-28-2023, 07:12 AM

Here's a random sampling. Writing kosync servers seems to be quite a popular pastime.

https://github.com/yeeac/kosyncsrv
https://github.com/jberlyn/kosync-dotnet
https://github.com/lzyor/kosync

Uncle Robin · 09-15-2023, 09:58 PM

Is the OTA server down again? I haven't used my Sage for a fortnight, powered it up and went to update, got the "Update Information not available on Development channel" message again.

Xaenor · 09-16-2023, 03:56 AM

Quote:

Originally Posted by Uncle Robin

Is the OTA server down again? I haven't used my Sage for a fortnight, powered it up and went to update, got the "Update Information not available on Development channel" message again.

Having the same problem.

Frenzie · 09-16-2023, 09:41 AM

Apparently so. https://github.com/koreader/koreader...ent-1722075351

Unfortunately I'm rather busy this week, otherwise I'd probably migrate it to a VPS of mine out of sheer annoyance with Azure.

Uncle Robin · 09-16-2023, 04:37 PM

Quote:

Originally Posted by Frenzie

Apparently so. https://github.com/koreader/koreader...ent-1722075351

Unfortunately I'm rather busy this week, otherwise I'd probably migrate it to a VPS of mine out of sheer annoyance with Azure.

Well then, I guess that leaves me with no choice but to actually use my Sage for reading - how awful!

Uncle Robin · 11-04-2023, 04:32 AM

Is there a time frame for a fix to the Dev Channel Update issues? I have given up trying every day, but even trying only once a week or less often, I still manage to get the "Update Information not available on the Developer Channel" every time I have tried in the last month

NiLuJe · 11-04-2023, 01:19 PM

That's a connectivity issue on your end

. (I mean, the main OTA server was down for a few days around the 25th, but that's no longer the case; and none of the mirrors were affected).

EDIT for clarification: the following applies to people experiencing that *right after a connection*, but for whom a retry or two fixes it.

(If your AP or router is a bit sluggish, the first few seconds of connectivity can be a fair bit spotty; this seems especially prevalent on Kobos. I've barely seen it happen since revamping my wireless network, FWIW).

Uncle Robin · 11-04-2023, 02:22 PM

Thanks for the explanation, I will give it another try

Uncle Robin · 11-05-2023, 05:31 AM

Recounting my experience in case it helps anyone else

I connected to WiFi, then after KOReader told me that it was connected, I waited a minute or two before trying to update. When I did press "update" a message came up saying "would you like to connect to WiFi?" Choosing the affirmative option led to KOReader attempting to connect, despite already being connected (according to its earlier message). When nothing at all happened after a couple of minutes, I turned WiFi off. I then repeated the exact same procedure and had the exact same result.

So then I tried something that has sometimes worked on previous occasions when KOReader wasn't connecting to WiFi. I exited into Nickel, connected to WiFi in Nickel and immediately restarted KOReader and pressed Update. It worked perfectly.

08-27-2023, 12:48 PM	#18
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	I don't really have anything against Redis & Openresty, they (well, Openresty really) just happen to be slightly more invasive and involved to deploy than a standalone Rust or Go binary (or a Python web app) (especially if you can't/won't use Docker; and both apply here: I'd have to mangle my kernel & systemd configs to even be able to run Docker, while I can pretty much isolate a random binary in a much clearer fashion with a simple systemd unit). And I'd have to mangle my already custom nginx & luajit ebuilds to just go native with OpenResty, as it isn't packaged in the main Portage tree. And, again, nginx configs. (And, also, running a whole OS layer in a container, even a slim one, just to run a 5MB daemon doesn't really jive well with me ;p). Last edited by NiLuJe; 08-27-2023 at 12:54 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[kosync-dotnet] KOReader Sync Server	jberlyn	KOReader	2	05-16-2024 07:49 AM
How to access web server hosted on NAS while using KOreader?	BMANN2	Kobo Reader	1	03-25-2023 02:14 PM
What KOReader sync server?	dmpop	KOReader	4	04-28-2022 08:17 AM
What content server for koreader ?	bunbury	KOReader	3	11-13-2021 06:53 AM
DX(G) Primitive fpt server android and Koreader	HoanPiTa	Kindle Developer's Corner	2	07-21-2019 11:54 AM

08-26-2023, 12:55 AM	#16
boox Member Posts: 12 Karma: 10 Join Date: Feb 2022 Device: Leaf 2, PB Touch HD3, Kindle PW2+JB, Android cell with KOreader	ota.koresder.rocks is online again.

08-28-2023, 07:12 AM	#19
Frenzie Wizard Posts: 1,752 Karma: 730681 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	Here's a random sampling. Writing kosync servers seems to be quite a popular pastime. https://github.com/yeeac/kosyncsrv https://github.com/jberlyn/kosync-dotnet https://github.com/lzyor/kosync

09-15-2023, 09:58 PM	#20
Uncle Robin Diligent dilettante Posts: 3,661 Karma: 52758936 Join Date: Sep 2019 Location: in my mind Device: Kobo Sage; Kobo Libra Colour	Is the OTA server down again? I haven't used my Sage for a fortnight, powered it up and went to update, got the "Update Information not available on Development channel" message again.

09-16-2023, 09:41 AM	#22
Frenzie Wizard Posts: 1,752 Karma: 730681 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	Apparently so. https://github.com/koreader/koreader...ent-1722075351 Unfortunately I'm rather busy this week, otherwise I'd probably migrate it to a VPS of mine out of sheer annoyance with Azure.

11-04-2023, 04:32 AM	#24
Uncle Robin Diligent dilettante Posts: 3,661 Karma: 52758936 Join Date: Sep 2019 Location: in my mind Device: Kobo Sage; Kobo Libra Colour	Is there a time frame for a fix to the Dev Channel Update issues? I have given up trying every day, but even trying only once a week or less often, I still manage to get the "Update Information not available on the Developer Channel" every time I have tried in the last month

11-04-2023, 01:19 PM	#25
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	That's a connectivity issue on your end . (I mean, the main OTA server was down for a few days around the 25th, but that's no longer the case; and none of the mirrors were affected). EDIT for clarification: the following applies to people experiencing that right after a connection, but for whom a retry or two fixes it. (If your AP or router is a bit sluggish, the first few seconds of connectivity can be a fair bit spotty; this seems especially prevalent on Kobos. I've barely seen it happen since revamping my wireless network, FWIW).

11-04-2023, 02:22 PM	#26
Uncle Robin Diligent dilettante Posts: 3,661 Karma: 52758936 Join Date: Sep 2019 Location: in my mind Device: Kobo Sage; Kobo Libra Colour	Thanks for the explanation, I will give it another try

11-05-2023, 05:31 AM	#27
Uncle Robin Diligent dilettante Posts: 3,661 Karma: 52758936 Join Date: Sep 2019 Location: in my mind Device: Kobo Sage; Kobo Libra Colour	Recounting my experience in case it helps anyone else I connected to WiFi, then after KOReader told me that it was connected, I waited a minute or two before trying to update. When I did press "update" a message came up saying "would you like to connect to WiFi?" Choosing the affirmative option led to KOReader attempting to connect, despite already being connected (according to its earlier message). When nothing at all happened after a couple of minutes, I turned WiFi off. I then repeated the exact same procedure and had the exact same result. So then I tried something that has sometimes worked on previous occasions when KOReader wasn't connecting to WiFi. I exited into Nickel, connected to WiFi in Nickel and immediately restarted KOReader and pressed Update. It worked perfectly.

Advert

Advert