[Bug]: Unknown error in client with self-hosted settings

Question

[Bug]: Unknown error in client with self-hosted settings

IrkinSh opened this issue 9 months ago · 13 comments

Hi folks,
I deployed self-hosted librum-server on Ubuntu Server 23.10 on my home network. The client has Windows 11 installed. I made changes to the registry according to the description. When I launch the client and try to register in the application, I get the error "An unknown error occured". What could be the reason?

Answer 1 · 2024-03-26T15:14:54.000Z

IrkinSh commented 9 months ago

Answer 2 · 2024-03-26T17:48:47.000Z

Hi all,

Got the same issue and similar setup.
Also in my case the Librum Server is deployed on an Ubuntu (22.04) machine.

The client is on a Windows 10 PC, and performed the changes to the registry (which, IMHO are a bad way to change configs, a Setting options or the ability to point to a specific URL from the client itself would be much better and user friendly) and when trying to login I'm getting the following

The translation is "Sorry" "Login failed, try again later".
Already tried to reboot the PC, same result.

I'm 100% sure that the self-hosted server is working as I've deployed a client on a linux machine and it worked flawlessy, created tags, folders as well as uploaded a couple of books in order to test.

So, at least in my case, the issue is with the Windows client.

Thanks!

Answer 3 · 2024-03-26T18:08:07.000Z

Thanks for reporting the issue. It would be great if you could provide the log file which is located at:

Linux: ~/.local/share/Librum-Reader/Librum/librum_log.txt
Windows: C:\Users<YOUR_NAME>\AppData\Roaming\Librum-Reader\Librum\librum_log.txt

Answer 4 · 2024-03-26T18:31:13.000Z

Thanks for reporting the issue. It would be great if you could provide the log file which is located at:

Linux: ~/.local/share/Librum-Reader/Librum/librum_log.txt

Windows: C:\Users<YOUR_NAME>\AppData\Roaming\Librum-Reader\Librum\librum_log.txt

log file from Windows 11
librum_log.txt

Answer 5 · 2024-03-26T20:35:10.000Z

And here the log from Windows 10

librum_log.txt

Let me know if you need also the logs from the Linux one.

Thanks

Answer 6 · 2024-03-26T20:40:38.000Z

And here the log from Windows 10

librum_log.txt

Let me know if you need also the logs from the Linux one.

Thanks

Ok, here it looks like some internal server issue. Can you also provide the server logs that are exposed via docker so I can see whats going on there?

Answer 7 · 2024-03-26T20:48:06.000Z

Here are the last 10k lines of server logs (i've renamed it to avoid confusion).
I don't think it goes much back as I've deployed it couple of days ago at max.

server_librum_logs.txt

Thanks

Answer 8 · 2024-03-26T20:55:02.000Z

Ok, so the issue seems to be caused by to the Products logic we have added some weeks ago. I'll look into solving this for self-hosted instances of Librum since we can't use the same logic for the production and self-hosted backend here.

Answer 9 · 2024-03-26T20:57:38.000Z

Ok, so the issue seems to be caused by to the Products logic we have added some weeks ago. I'll look into solving this for self-hosted instances of Librum since we can't use the same logic for the production and self-hosted backend here.

Will wait for it then!

PS: as mentioned, seems related to just the Windows client as with the Linux one (installed through flatpak / flathub) works fine, currently got a session opened on it

Thanks!

Answer 10 · 2024-03-26T21:01:43.000Z

Hm, are you using the same server for both clients? This should not be a client issue, but a server issue.

Answer 11 · 2024-03-26T21:09:47.000Z

Hm, are you using the same server for both clients? This should not be a client issue, but a server issue.

Yep, same server for both.
Basically my path up to now was:

Deploying the Librum-Server selfhosted
Trying the Windows client on the laptop => got the error described above
Setup the Linux client on a virtual machine running Ubuntu 22.04 (to be fair, it's WSL machine / instance, so not properly a vm, but got the client up and running there) => up and running and currently using it
Tried to install the client on the desktop => got again the error described above

All three client pointed (and currently are poiting) to the same server instance.

If from your side, this should be a server side issue, then I suspect the Linux client is ignoring the "product" part you mentioned earlier (my assumption).

Thanks

Answer 12 · 2024-04-12T16:48:43.000Z

Hey there,

Any update on this one?
I've seen that there was both a Docker update as well as Windows (0.12.2, when I replied to the issue I had 0.12.1 installed).
Tried to update them both but no changes, the behavior on Windows is still the same.

On linux it continues to function (semi) properly.
Semi as a couple of books I've added to the client are not being syncronized on the server (but this is a separate matter).

Thanks!