[Bug Report] OPDS Android app Librera Reader 404 book not found and web .../opds error

[VegethB]

On the android app you can navigate the library (you only see the names of the series and the volumes, no covers) you can select volumes and chapters but as soon as you open one of them comes out 404 book not found. If you write on your browser / opds this error comes out:

EDIT1 Android Screen Librera:




Android Screen PocketBook:


Visualization as soon as you click on the server name (mango) in theory you should see the series library.

Environment (please complete the following information):

• OS: Windows and Android 9.0 Lineage OS Galaxy S5
• Browser chrome
• Mango Version 0.7.1

**Docker

• The docker-compose.yml file you are using, or your .env file. Same of issue [Bug Report] Slow scan with large libraries on Hyper-V Docker (Windows) #79

While we're here ... To update the docker with new releases, without losing the configuration and all the settings. Which method do you recommend?

[short-circuit]

I am having the same issue with KyBook3 and iOS. Thought in the beginning it might be a reverse proxy problem, but OPDS doesn't work on LAN either. No errors in logs either until now.

[VegethB]

I have tried 3 different apps with OPDS support via network (SAMBA and http) but only Librera makes you scroll through the series. The other apps load endlessly after entering the password (e.g. PocketBook). The http version of the base site instead works wonderfully (the one without OPDS).

[hkalexling]

You got the XML error on the /opds page because one of the manga names contains the ampersand character (&) and Mango didn't escape it properly. This will be fixed in the next version. Thanks for reporting!

The 404 error is a separate issue and I couldn't reproduce it. Can you access the page /opds/book/[id] in your browser?

To update the image, simply use docker-compose pull mango to download the new image and start it with docker-compose up. The user configuration and library are stored on the host system as mapped volumes so they won't be affected.

[VegethB]

Volume1.

---

Series list:

[hkalexling]

@zFerry98

1. When loading the page, there should be an error message printed in your console. Could you copy and paste it here?
2. Can you open the "Volume 01" folder in the non-opds site (i.e., /book/[the_same_id] without the /opds/ prefix)?

[VegethB]

@zFerry98

1. When loading the page, there should be an error message printed in your console. Could you copy and paste it here?
   - I have enabled debug output:
   
   - This instead putting info on output:
   

LOL You just don't recognize .zips? Strange because I also have CBZs.

---

2. Can you open the "Volume 01" folder in the non-opds site (i.e., /book/[the_same_id] without the /opds/ prefix)?
   - Only OPDS doesn't work. The normal library works all:
   
   

[hkalexling]

Ah, I see the problem. It looks like Alpine (the base OS of the docker image) doesn't provide a MIME types registry, and so Mango failed to get the MIME types of the archive files. I will push a new release that fixes this soon.

[hkalexling]

Both issues are now fixed in v0.7.2. Thanks for reporting!

[VegethB]

As I imagined, the best option is to use a machine with linux 64 (like ubuntu server or distro lite) than the docker. Which is a mess having a windows server. The problem is that I have no x64 pc but only x32 to use as mules. You say it works if you use linux bash support mode in windows? That function that adds a minimum of functions to run the terminal and the basic functions of a linux subsystem.

[hkalexling]

@zFerry98 No it's not a Windows issue. The new release should work in your current setup (Docker on Windows) and the two issues you reported should be fixed now.

[VegethB]

No it's not a Windows issue. The new release should work in your current setup (Docker on Windows) and the two issues you reported should be fixed now.

No, I explained myself wrong. I meant that being a software for linux rather than for windows, it is better to run it directly on a real OS than on virtual machines. Having no more than 16gb of ram, since I put dockers I am always at 80 90% used. Running the server directly or having to dedicate Core and ram to virtualize an x64 pc with OS is certainly a part of the slowness problems. For now I have closed some services that I no longer use to recover resources. Anyway, thanks for the quick and perfect support 👍

[jaredlt]

@zFerry98 Just to let you know, I run Mango via WSL (Windows Subsystem for Linux) and haven't had any issues. I haven't actually measured it but it certainly seems to be less resource hungry than via Docker.