My epub files pass epubcheck, but Kindlegen refuses to generate mobi files. It seems that issue is caused by adding references ("colophon", "dedication", etc.) to pages.

I'm really hitting a wall here. I would really appreciate some EPUB

FILE + ERROR LOGS: https://we.tl/UtGqtAxbir

  • 2
    Hi and welcome on this site; I've read your question and it is not clear what your problem is or what you are asking here; and, linking to a downloadable file without even explaining what it is supposed to be is not a good practice. You should try to improve your question.
    – Sekhemty
    Commented Feb 16, 2017 at 20:34

6 Answers 6


I had the same problem, was caused by repeated chapters.

  • Do you mean: "by including two versions of the same chapter." Commented Apr 15, 2017 at 14:44
  • yes, by mistake I was repeating the same chapter twice in the TOC. Commented Apr 17, 2017 at 18:27
  • This was my issue as well, although I didn't grok your answer at first -- it would have been more clear to say 'it was caused by duplicate chapter names'.
    – Ben
    Commented Feb 20, 2018 at 3:41

I hit the same problem today. The problem appeared to be that the links in the nested (or

  • for EPUB3, no difference) pointed to locations other than the parent element.

    So this code caused the same error you got: enter image description here The key is that, because of a quirk in InDesign export, the section head was created as a separate file. I went in and put the items into pessoa_book_of_disquiet_text-8.xhtml, like so

    enter image description here Voila, no more error. It looks like for Kindle, nested content has to be in the same file as the parent. To be clear, I had to move all the content into the file, not just change the names.

    Does this fix your problem?


    The key error is here:

    Error(prcgen):E24011: TOC section scope is not 
    included in the parent chapter:Table of Contents

    I'm not 100% sure what this means. Perhaps 5824-Section.xhtml seems to be causing the issue. (I'm assuming).

    It's very strange that the epub file validates. This is probably an issue with Kindlegen, but there are times when Calibre is incompatible with kindle.

    Probably the strangest thing to me when I examine your epub file is that toc.xhtml (on line 24) lists itself as an item in the TOC. Why is it linking to itself? That is definitely something which might confuse Kindlegen.

    Kindle requires a virtual table of contents at the front of the ebook, and your toc.xhtml would normally contain links to all the chapters. This one does not do that.

    Unfortunately while it is relatively easy to figure out epub issues, Kindlegen sometimes produces strange errors, and the best solution is to keep removing chapters until you get a version that works. Then try to figure out why.

    Remember that with epubs you can rename them to zip files and then unzip the files to examine everything.


    It seems that kindlegen does not like duplicated names in the TOC. I ran across this issue and was only able to resolve when I renamed one of my headers. For reference, I am using Pandoc to generate the ePub file, with a TOC depth of 3. In this particular case, I had an H2 and an H3 with the same name. I renamed the H3 to be unique and the problem disappeared.


    Thanks to this thread I managed to solve the same issue. It may be a really (pre-covid!) old thread now but i thought I'd add how i did it in case anyone else struggles. Open Calibre Click on Edit Book Click on Tools Open TOC (Table of Contents) Click 'Edit TOC' Down the left side will be 'openable' chapters, open them up one by one and highlight 'Untitled' and move across to the right and click 'Remove Entry'. Do this for all the Untitled entries and/or anything repeated and then click ok and re-save your book. This should then open as an EPub.

    I hope this helps someone.



    some chapters are linking same name or same id that's called an error.

    for example:

  • Chapter 1
  • Chatper 2

    Your Answer

    By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

    Not the answer you're looking for? Browse other questions tagged or ask your own question.