Hi.
I'm trying to open some of the .epub files which are in my calibre library. When pressing the 'eye' icon beside the .epub file instead of opening the book ready to read in the new tab (like it usually works) it opens new tab with next error:

This happens with some of my .epub files while other work as expected. Also it doesn't show the cover of these books (Although they persist in the file and show up in Calibre).

What is the reason of such a strange behavior?

Some users already sent me reports like this. You can check all your calibre database with this url : http://[YourSynologyIpOrDomain]/cops/checkconfig.php?full=1

This can take some time depending on your library size. It will check the accessibility of every books in your library and report every unreadable books.

I've seen some old Calibre databases where there were some case discrepancies between the path and filename stored in Calibre's database and the real path and filename on the filesystem (no problem on Windows but problems on Synology or any other Linux based OS).

Some directories may also have different access rights causing problems.

This can be also errors on the files itself.
On Callibre go to 'Refine Books' to verify all your epubs.
There you can update metadata and covers.

Of course you're right.
Seeing that @Drewshg312 also didn't see the covers of these books made me guess it was a bigger problem.

Let's wait for more information from him ...

Hi!
I've forgot to say, I'm using cops on Synology DS215j, DSM 6.0.2-8451 Update 7.

So I've done the cops check and got this information:

Also the Calibre > Books > Library Maintenance > Check Library shows everything is fine..

Did you executed the 'Refine books' on Calibre?
Make a copy of your local Calibre library first and then upload the 'refined' one.

~I do remember that once had a similar problem, with some of the epubs not loading its covers.
You should also verify if the books with issues are always the same (or test in a different setup as in a local LAMP or WAMP install).

@Drewshg312

So it seems I was right :(, All the books listed here are not readable by COPS. The path shown here is what is stored in Calibre's database. Please check using Synology filemanager or any Linux computer if these paths exists in your Nas or if there is some case difference.

If there is no case difference then the problem should come from access rights.

horus68, I'm using Calibre on mac. Unfortunately I didn't find any 'Refine books' menu option. The only one I've found is 'books > Library Maintenance > Check Library'

seblucas, I've checked a couple times - files are existing and their permissions are the same as of those files, which are working well.

@Drewshg312 using windows but try to add the button to the toolbar (mine is in Portuguese but will try to translate and follow with pics: the icon its a 'yellow broom'

In the main toolbar click Preferences / Change Calibre behaviour
Click Toolbar

Choose the Main toolbar

Find the refine book icon and move it to the main toolbar

And it will show on your toolbar to execute

@horus68 Thank you very much! It's now called 'Polish books'. I didn't know about such a useful feature!!!! That's awesome. Although it did not help((((( I don't understand what can be wrong with the book… It's opening great both on my mac (iBooks) and on my Kindle Voyage, encoding shows no visible problems… This is very strange - some epubs just work, others - not. And seems like it's a COPS problem because all of them work on all devices and don't work in cops…

Actually, I've noticed strange thing:
after running 'Polish books' those books which were broken before now can't be even downloaded by clicking their format 'EPUB' for example - it just shows 404 error:

But the actual files (.epub, .fb2, .azw3 and others) are still in the calibre database... so COPS just sees what's inside the directory, but refuses to read and download these books

Lets try a different way:
Create a new empty Calibre library and copy there only the ebooks with issues (use calibre 'copy to library')
then setup a new COPS on your local test server. This way you can rule out the actual server setup and permissions. Then move on to each file (renaming the file to avoid spaces and special letters and so on. There must be an error somewhere.
You can also some of your books issues so others can see whats going on.

@horus68, sorry, I just didn't understand... you want me to post some of the books which cause issues?

You have some with issues, some are ok (lets call it Calibre library A published in Cops install A) .
The issues can be on:

• your ebooks
• on Cops
• on server.

You need to rule each one out! So lets simplify the problem and start working only on those ebooks with issues:

• Create a new Calibre library (lets call it library B)

• Copy the ebooks with issues tho library B (Clibre right button on a ebook and choose 'copy to library'.
  So now you have a library with the ebooks with issues.

• Now install a new Cops (lets call it 'Cops install B') for library B.
  Host the new COPS on a local web server (an Apache-MySQL-PHP setup for tests as in MAMP for Mac)

Now we can talk on problems and solutions:

• If the problem is located on ebooks the problem will be the there too in library B and for all ebooks inside it.
• If the ebooks are fine in install B then the problem is on your server (the installation A)

And we will move from there! Until then is just speculation and there is no easy fix for all!

Rule of thumb: never publish a site or anything online before testing it on your MAMP / LAMP setup

@horus68, So I've created the new calibre database on my Synology NAS (/volume1/bookz_test/), with some books which cause issues and while running new instance of COPS I've got this:

Here /volume1/books/ - my main library.
/volume1/bookz_test/ - my test library with books which cause issues only.

Seems like even after uninstall and manual removing of /var/services/web/cops/ directory it still remembers something about previous COPS configuration somehow....

What am I doing wrong?

So seems like it takes /volume1/books/ as my open_base_dir variable. Where can I change that variable? As I've said before, I use dsm 6.0.2 so I don't see 'Control Panel -> Web Services -> Web Applications' option anymore... Which file should contain this variable?
I've got this kinda application:
But it shows this:

open_basedir = none instead of /volume1/books... So it's probably not the one we need...

Still don't understand why the newly installed COPS forces me to put my library into /volume1/books?

All I want to do is rule out the issues regarding some of your ebooks to make sure they are fine or not.
I consider that we didn't ruled out the possibility of the issue is related to each ebook.
In the past I had a similar issue on some ebooks and fixed it. That's what I can add to the table here.
But it seems that you prefer to focus on the server configurations. There could be a solution there but I don't know if other issues are not there too.
As I do not have a NAS, I can't help you out. Maybe other user can help you out

I've fixed it - there was a server problem - permissions for http group. But still don't understand how to change the library path. Why COPS forces me to put my library into /volume1/books?

Great that you found the error

If you want to use another directory you just have to change open_base_dir (see : https://github.com/seblucas/cops/wiki/Howto---Synology)

Did you install the Synology package or did you install it manually ?

The synocommunity package does some voodoo to add the directory you specify during the installation. Maybe it does not work with latest DSM ?

I noticed a problem with titles that contain commas. For me, the download URL:

produces a 404 error. However, if I remove both %2C (comma) from the URL, it downloads just fine. I played a bit around and noticed that the RewriteRule to the fetch.php gets ignored as soon as I add a comma to the URL. You can test this with: /download/2713/%2C.mobi which gives a 404, and /download/2713/.mobi which works fine. I don't know why this happens, but it seems to be a problem with Apache.

I don't use Apache and I can confirm that it work fine with Nginx, see :

EDIT: sorry wrong link

It seems my problem comes from a bug in the Caddyserver I use to get https to the outside world. See caddyserver/caddy#1362 .

let's close it then