Manga pages won’t load
-
@swoods I would also suggest trying with your phone using cellular data instead of wifi (assuming that's an option for you), or through the VPN of your choice. That's what I have to do to read pre-pubs from my parents' house; ISPs can block the weirdest things, and your home's internet connection is about the only common factor once you've tried from multiple computers...
-
@swoods said in Manga pages won’t load:
@Geezer-Weasalopes Thanks for your reponses! It's a lonely feeling when you post on a forum and no one replies. I appreciate it.
That's one of the reasons I've been chiming in, truth to tell.
To let you know someone had read and was concerned.The tech advice has been a bit of flailing around going "Um, if I were Tech Support what would I ask for?" followed by "OK, having gotten info I should at least check how the same works with my setup."
And if you prime the pump enough others tend to join in.
-
@kuali said in Manga pages won’t load:
@swoods I would also suggest trying with your phone using cellular data instead of wifi (assuming that's an option for you), or through the VPN of your choice.
Thanks @kuali. I will try both approaches if I fail out with my various browsers. I also have a machine where I can set up a proxy; that's also on my list to try.
Mindboggling that you get problems with prepub volumes. I'll go back and check if that matches how it works for me.
-
@Geezer-Weasalopes, truly appreciated!!!
I haven't had any issues with the platform up until this point. And, to be fair, I don't know if this is due to a change in the platform or if I changed something on my end.
If I did make some configuration change I am completey puzzled why it only affects newer manga chapters.
I do have a test computer and I may do a complete build with a new Linux OS and browser. That way there would be no legacy data from profiles, config settings and such... kind of a last resort.
-
I’m also having this problem and have been since the end of February.
-
I too have noticed this while trying to read the latest chapters of Coppersmith's Bride. Reading on a Mac, browsing with Chrome.
-
Having worked on my problem with Firefox, I have found a fix that works on my Linux machine.
Firefox has "Advanced Preferences" that you can access (not recommended, they say) by typing about:config into the URL bar. A huge list of items comes up and if you change the boolean "privacy.resistFingerprinting" item to FALSE, then the new pages will load on Linux. When you change it back to TRUE, manga pages stop loading.
Unfortunately this doesn't work on the Mac. I don't know why.
This is not something I feel comfortable with changing permanently, but I feel like I'm one step closer to making it work.
-
Bumping up this post because I've had this issue for a while now. Firefox won't load manga pages. Things that will:
- Edge
- Chrome
- Private Session Firefox
I don't know what else to try. I've tried disabling all of my extensions already, so I'm fairly certain they aren't the fault on their own.
Any help or wisdom will be appreciated. -
@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.
-
@chocolatkey I have confirmed that I don't have resist fingerprinting on, in case my situation can help with looking at the issue.
-
@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
-
@chocolatkey https://imgur.com/a/YaOkG3B
There's the console tab open. -
@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. -
@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. -
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.
-
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.
-
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-J34NYNQThis 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. :-)
-
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 ResolutionSystemI'm still on Firefox 137.0.1 on Linux.
-
@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.
-
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.resistFingerPrintingonce the chapter is loaded and the reader works fine going from page to page.Third, by switching the
privacy.resistFingerPrintingon 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...
