J-Novel Club
    • Categories
    • Recent
    • Tags
    • Users
    • Login

    Manga pages won’t load

    Scheduled Pinned Locked Moved Support
    58 Posts 17 Posters 40.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • chocolatkeyC
      chocolatkey Staff @swoods
      last edited by

      @swoods I can confirm that if you turn on resist fingerprinting, the reader won't load. I hadn't tested Firefox with that setting before. I'll take a look into what's causing it.

      A 1 Reply Last reply Reply Quote 0
      • A
        Anaxim Premium Member @chocolatkey
        last edited by

        @chocolatkey I have confirmed that I don't have resist fingerprinting on, in case my situation can help with looking at the issue.

        chocolatkeyC 1 Reply Last reply Reply Quote 0
        • chocolatkeyC
          chocolatkey Staff @Anaxim
          last edited by

          @Anaxim If you are unable to read manga in Firefox with the fingerprint resistance disabled, then that's not something I can reproduce locally. If you could send me a screenshot of your browser's dev tools "Console" tab, that could potentially help narrowing down the cause

          A 2 Replies Last reply Reply Quote 0
          • A
            Anaxim Premium Member @chocolatkey
            last edited by

            @chocolatkey https://imgur.com/a/YaOkG3B
            There's the console tab open.

            1 Reply Last reply Reply Quote 0
            • A
              Anaxim Premium Member @chocolatkey
              last edited by Anaxim

              @chocolatkey Following a Google search, I tried disabling cache in the network tab of the dev tools. That actually did the trick and let me load manga chapters. Hope this helps in figuring out the issue.
              Also cleared site data for JNC in general and that also did the trick.

              chocolatkeyC 1 Reply Last reply Reply Quote 0
              • chocolatkeyC
                chocolatkey Staff @Anaxim
                last edited by chocolatkey

                @Anaxim So you're saying a one-time clearing of the site data fixed it permanently?
                The console tab unfortunately didn't reveal any error.

                A 1 Reply Last reply Reply Quote 0
                • C
                  Cyberdodo
                  last edited by Cyberdodo

                  I'll add my own results. I've tried this using 2 different computers, one running Linux and the other Windows 11.
                  On the Linux PC, I tried Brave and Floorp (a Firefox fork). Both browsers refused to load images for any mangas, new or old.
                  On the Windows PC, I tried Brave, Tor, and Edge. Brave and Tor both failed to load images for any manga. However, I was able to read mangas using Edge.

                  Since Edge works, but is the only browser I have that does, it looks to be a security/privacey issue.

                  I'm not happy with using Edge as a workaround though. I hate Edge with the fury of a thousand suns! Ok, I'm exaggerating, but I don't trust Edge even as far as I could throw a wooly mammoth using a toothpick.

                  1 Reply Last reply Reply Quote 0
                  • S
                    swoods
                    last edited by

                    Unfortunately manga pages in Firefox have stopped loading for me.... even when privacy.resistFingerPrinting is set to FALSE.

                    Older manga pages used to load in all cases, but they are now also broken.

                    I'm now at Firefox 137.0.1.

                    1 Reply Last reply Reply Quote 0
                    • S
                      swoods
                      last edited by

                      Looking at the web console, maybe it's worth noting that I'm no longer getting "Cross-Origin Request Blocked" errors. So that feels like a genuine advance.

                      I am seeing a new error:
                      The resource at “https://labs.j-novel.club/embed/v2/75171192225d219a4941.svg” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. PRT-J34NYNQ

                      This seems to be in regards to https://labs.j-novel.club/app/v2/me

                      I also get these warnings:
                      Preload of https://labs.j-novel.club/embed/v2/qsc_worker.js?v=1.0.2 was ignored due to unknown “as” or “type” values, or non-matching “media” attribute. PRT-J34NYNQ
                      Preload of https://labs.j-novel.club/embed/v2/drm_worker.js?v=1.0.2 was ignored due to unknown “as” or “type” values, or non-matching “media” attribute.

                      And I failed to mention in my last post, all of the novel pages are still loading just fine. Only manga pages fail.

                      Hope this helps! Thanks for working on this issue. :-)

                      1 Reply Last reply Reply Quote 0
                      • S
                        swoods
                        last edited by

                        Sorry to take up bandwidth here. I just wanted to report that my Firefox behavior is back to where manga pages load when privacy.resistFingerPrinting is set to FALSE
                        -- but fails when set to TRUE.

                        When this configuration is set to TRUE I am now seeing a set of 404 errors like this one
                        HEAD https://labs.j-novel.club/app/v2/me/follow/SER-N2HXYOA
                        Status 404
                        Version HTTP/2
                        Transferred 1.08 kB (0 B size)
                        Referrer Policystrict-origin-when-cross-origin
                        DNS ResolutionSystem

                        I'm still on Firefox 137.0.1 on Linux.

                        1 Reply Last reply Reply Quote 0
                        • A
                          Anaxim Premium Member @chocolatkey
                          last edited by

                          @chocolatkey Really sorry about how long this took to answer. Kinda forgot about the thread. Yes, that is what happened. Manga has loaded without issue since.

                          1 Reply Last reply Reply Quote 0
                          • S
                            swoods
                            last edited by swoods

                            More debugging information. This is from Firefox 137.0.2-1 as installed on my linux (Debian, PopOS) laptop.

                            First, I tried disabling cache and clearing site data, but unlike @Anaxim's experience this didn't help on my instance.

                            Second, I wanted to clarify that the problem with the manga reader on Firefox is strictly limited to loading the chapter. Once loaded, I can move from page to page without problems. That is, I can turn on privacy.resistFingerPrinting once the chapter is loaded and the reader works fine going from page to page.

                            Third, by switching the privacy.resistFingerPrinting on and of during load, I've isolated this error:

                            Uncaught Error: Permission denied to access property "type"
                            NextJS 5
                            Learn more
                            framework-717b5372727d76c7.js:25:92626
                            NextJS 4
                            forEach self-hosted:157
                            D NextJS
                            sendSyncMessage moz-extension://e1185278-3333-41bb-aefd-8b59cabfee08/nscl/common/SyncMessage.js:564
                            refetch moz-extension://e1185278-3333-41bb-aefd-8b59cabfee08/content/staticNS.js:126
                            fetchLikeNoTomorrow moz-extension://e1185278-3333-41bb-aefd-8b59cabfee08/content/staticNS.js:144
                            fetchPolicy moz-extension://e1185278-3333-41bb-aefd-8b59cabfee08/content/staticNS.js:95
                            fetchPolicy moz-extension://e1185278-3333-41bb-aefd-8b59cabfee08/content/staticNS.js:85>

                            The "learn more" link says, among other things, that :

                            "There was attempt to access an object for which you have no permission. This is likely an <iframe> element loaded from a different domain for which you violated the same-origin policy."

                            Thanks again, @chocolatkey , for your efforts. Hope this helps...

                            1 Reply Last reply Reply Quote 0
                            • N
                              Nekoatl Member
                              last edited by

                              I could read manga pages just fine as of 2 days ago, but now, any manga chapter I open gets stuck on "Fetching info...".

                              N 1 Reply Last reply Reply Quote 0
                              • N
                                Nekoatl Member @Nekoatl
                                last edited by

                                It's working again.

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  swoods @Nekoatl
                                  last edited by

                                  @Nekoatl -- did you change anything in your browser? Or did the application spontaneously start working again?

                                  N 1 Reply Last reply Reply Quote 0
                                  • N
                                    Nekoatl Member @swoods
                                    last edited by

                                    @swoods It spontaneously started working again. I assumed it was a temporary service outage, but now I'm seeing the same problem. Interestingly, it's happening on a Friday morning, same as last time. I expect it'll start working again within an hour.

                                    1 Reply Last reply Reply Quote 0
                                    • N
                                      Nekoatl Member
                                      last edited by

                                      My prediction was wrong. It's still not working.

                                      1 Reply Last reply Reply Quote 0
                                      • N
                                        Nekoatl Member
                                        last edited by

                                        Just to be thorough, I tried restarting my computer and clearing cookies, but of course neither helped.

                                        1 Reply Last reply Reply Quote 0
                                        • N
                                          Nekoatl Member
                                          last edited by

                                          It just started working again.

                                          S 1 Reply Last reply Reply Quote 0
                                          • S
                                            swoods @Nekoatl
                                            last edited by

                                            @Nekoatl, so it sounds like something is changing on the platform rather than on your computer. Anyway, I hope it keeps working for you!

                                            What browser are you using? And do you have any browser extensions or VPN or such?

                                            N 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 3 / 3
                                            • First post
                                              Last post