OTA updates not available?

[Uncle Robin]

My Sage is on Stable, my Libra H2O on nightly. When I try to update my Sage I get "update information not available on Stable channel" When I try on my Libra H2O, I get "unable to contact OTA server. Try agan later or try another mirror" Is there a timeframe for a fix on this?

[pazos]

While https://github.com/koreader/koreader/issues/10615 is still open the same issue might happen month after month: the server that runs the entire koreader.rocks infrastructure gets killed because it exceeded the network bandwith.

That affects OTA updates, dictionary donwloads, the sync server and maybe others?

The server always returns back to life during the 26th of each month.

[pazos]

Using mirrors for OTA updates doesn't help as mirrors rely on the main server to fetch updates to mirror

But that might explain the two different messages you're seeing, I really don't know.

[Uncle Robin]

Originally Posted by pazos

While https://github.com/koreader/koreader/issues/10615 is still open the same issue might happen month after month: the server that runs the entire koreader.rocks infrastructure gets killed because it exceeded the network bandwith.

That affects OTA updates, dictionary donwloads, the sync server and maybe others?

The server always returns back to life during the 26th of each month.

THanks for that, I'll mark the 26th on my calendar.

[Ebookus]

Originally Posted by pazos

While https://github.com/koreader/koreader/issues/10615 is still open the same issue might happen month after month: the server that runs the entire koreader.rocks infrastructure gets killed because it exceeded the network bandwith.

That affects OTA updates, dictionary donwloads, the sync server and maybe others?

The server always returns back to life during the 26th of each month.

interesting. who pays for the servers?

[rantanplan]

Originally Posted by pazos

That affects OTA updates, dictionary donwloads, the sync server and maybe others?

So that explains why I couldn't login to the official sync server. I switched to an alternative sync server, and I'm quite happy with it. I think about hosting my own but docker support immediately puts me in a higher pricing tier :-/

[pazos]

Originally Posted by rantanplan

So that explains why I couldn't login to the official sync server. I switched to an alternative sync server, and I'm quite happy with it.

I think you're talking about https://kosync.ak-team.com:3042, which is maintained by NiLuJe. If not please share your alternative one, to be aware of it.

I spawned another instance in https://kosync.duckdns.org. Each instance keeps its own database, so it's not an option to switch between them often.

Just select one that works for you, setup your KO devices to use all the same instance and have fun.

Originally Posted by rantanplan

I think about hosting my own but docker support immediately puts me in a higher pricing tier :-/

Both the alternative servers are based on a single rust binary, which is easier to deploy and does not require docker or any other complex setup. Just a recent enough rust compiler.

[rantanplan]

I'm using https://kosync.rustysoft.de/

[pazos]

Oh, great! I didn't know about this one. He's using its own implementation at https://git.rustysoft.de/martin/kosyncrs

[Frenzie]

Not a bad Gitea theme. Or maybe Forgejo changed the default a bit to look different?

[beedaddy]

Originally Posted by Frenzie

Not a bad Gitea theme. Or maybe Forgejo changed the default a bit to look different?

Yes, it's forgejo's default theme.

(Ah, and I moved kosync.rustysoft.de to a new server a few days ago. I just noticed then, that it is used by a few other people. I hope that the move has not caused any problems for them.)