You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The plugin is giving 403 error, correct? The plugin has already been migrated to the novel nice domain. You can check that if you open the site in webview.
The plugin is giving 403 error, correct? The plugin has already been migrated to the novel nice domain. You can check that if you open the site in webview.
Have you read what i said? And why are repeating what i already said?
What are you talking about? You didn't mention that the site was giving 403 error so I was trying to confirm because I had some issues with the app at the moment. You also didn't mention that the domain has already been changed in the plugin. So, follow your own advise and read what I said I'm not repeating you
What are you talking about? You didn't mention that the site was giving 403 error so I was trying to confirm because I had some issues with the app at the moment. You also didn't mention that the domain has already been changed in the plugin. So, follow your own advise and read what I said I'm not repeating you
I mentioned above dawg that the domain has changed and isn't it natural that the site will give 403 error if the domain has been changed?
As i can see there is no update, so I'm not sure if the domain has been changed in the plug in the app… and i haven't seen cloudflare protection on the app tho…
From what I can see the domain has been updated. The issue is the 403 error. I just wanted to confirm whether the error was only on my end because none of my plugins were working at that time. A simple yes would have saved us both a lot of time
From what I can see the domain has been updated. The issue is the 403 error. I just wanted to confirm whether the error was only on my end because none of my plugins were working at that time. A simple yes would have saved us both a lot of time
Did the plugin ever work after the domain changed to nice novel. The website is straight up blocking the plugin. I tried using headers just to check if it would even work but that didn't work either the 403 error still persists. I'm trying to see what changed in the website that is causing this
Did the plugin ever work after the domain changed to nice novel. The website is straight up blocking the plugin. I tried using headers just to check if it would even work but that didn't work either the 403 error still persists. I'm trying to see what changed in the website that is causing this
Man i have never seen it open up after the domain change, but idk what kind of black magic they are using to block our plugin 😭.
Did the plugin ever work after the domain changed to nice novel. The website is straight up blocking the plugin. I tried using headers just to check if it would even work but that didn't work either the 403 error still persists. I'm trying to see what changed in the website that is causing this
Should i open a new issue and try to involve more people in it?
If migrating fixes your issue, then that would be better but if migrating breaks your history or downloaded chapters then it might be better to raise an issue and hope someone fixes it. Whichever you think is better
Then this plug-in definitely need a new request…
I have like at least a few thousand chapters downloaded from this extension like maybe 4000+
The 403 error for box novel is easy to fix, but definitely not user friendly or "logical" at all, to fix, open boxnovel using webview, go to the searching box, write anything there and click in search, observe is not to click on the results but in the search button itself, after that it will show you a cloudflare box, conclude it, and it's done, you just need to refresh in the app and everything will show just fine now, for some strange reason this only happens if you try to search something in the app, update the novel to see if new chapters are available or read the Novel itself works just fine
Guys, could you please tell me if anyone is having issue in the chapter list? For some reason certain novels with 100+ chapters sometimes just don't know the correct sequence, even trying the latest lnreader one is not working, even getting the latest on commit, I just don't know if this is a plug-in issue or a lnreader issue, where should I open a bug report for this? I'm inclined to believe is a plug-in one because it only happens for box novel, and for reference in the website the chapter list is correct, but lnreader don't get the proper order for some reason
Yeah i also saw that, some novels are just fetching only 200 or some chapters no matter how many times i refresh, and also, there is a problem of me being unable to update my library, the novels aren't connecting at all with the plugin that are in my library… throwing errors and not updating at all, what the fuck has the owner done with the website…
Yeah i also saw that, some novels are just fetching only 200 or some chapters no matter how many times i refresh, and also, there is a problem of me being unable to update my library, the novels aren't connecting at all with the plugin that are in my library… throwing errors and not updating at all, what the fuck has the owner done with the website…
Can you reference what novels you have found that fetch only 200 chapters?
Yeah i also saw that, some novels are just fetching only 200 or some chapters no matter how many times i refresh, and also, there is a problem of me being unable to update my library, the novels aren't connecting at all with the plugin that are in my library… throwing errors and not updating at all, what the fuck has the owner done with the website…
Can you reference what novels you have found that fetch only 200 chapters?
@K1ngfish3r the source https://novelnice.com/ has set up its Cloudflare check specifically on the search/listing https://novelnice.com/?s=&post_type=wp-manga endpoint rather than the homepage potentially to block this plugin. While this can be solved by opening the WebView, then manually navigating to search from inside it to trigger and solve the challenge this is not really intuitive or convenient. In the application, BrowseSourceScreen's handleOpenWebView hardcodes url: plugin.site, so there's currently no way for a plugin to tell the webview to open a different URL. Is there some way to fix this issue?
Activity
D3ICIDE commentedon Aug 1, 2026
The plugin is giving 403 error, correct? The plugin has already been migrated to the novel nice domain. You can check that if you open the site in webview.
torkita commentedon Aug 2, 2026
Have you read what i said? And why are repeating what i already said?
D3ICIDE commentedon Aug 2, 2026
What are you talking about? You didn't mention that the site was giving 403 error so I was trying to confirm because I had some issues with the app at the moment. You also didn't mention that the domain has already been changed in the plugin. So, follow your own advise and read what I said I'm not repeating you
torkita commentedon Aug 2, 2026
I mentioned above dawg that the domain has changed and isn't it natural that the site will give 403 error if the domain has been changed?
D3ICIDE commentedon Aug 2, 2026
The plugin has been updated with the new domain. What part of this do you not understand. The 403 error is probably cloudflare blocking it.
torkita commentedon Aug 2, 2026
As i can see there is no update, so I'm not sure if the domain has been changed in the plug in the app… and i haven't seen cloudflare protection on the app tho…
D3ICIDE commentedon Aug 2, 2026
From what I can see the domain has been updated. The issue is the 403 error. I just wanted to confirm whether the error was only on my end because none of my plugins were working at that time. A simple yes would have saved us both a lot of time
torkita commentedon Aug 2, 2026
Yeah i have also checking it out a few moments ago, and it has been updated, but what can be causing the 403 error?
torkita commentedon Aug 2, 2026
#2205 (comment)
Check it out.
torkita commentedon Aug 2, 2026
Bro it is using some cloudflare protection bit idk what type of protection it is using, when going through webview the captcha doesn't appear too.
@D3ICIDE
D3ICIDE commentedon Aug 2, 2026
Did the plugin ever work after the domain changed to nice novel. The website is straight up blocking the plugin. I tried using headers just to check if it would even work but that didn't work either the 403 error still persists. I'm trying to see what changed in the website that is causing this
torkita commentedon Aug 2, 2026
Man i have never seen it open up after the domain change, but idk what kind of black magic they are using to block our plugin 😭.
torkita commentedon Aug 2, 2026
Should i open a new issue and try to involve more people in it?
D3ICIDE commentedon Aug 2, 2026
wait for like 6 hours if it isn't fixed by then it means I can't fix it after that you should open a new issue with all details
torkita commentedon Aug 2, 2026
Ohk dawg, bro you locked in asf.
13 remaining items
torkita commentedon Aug 2, 2026
Then this plug-in definitely need a new request…
I have like at least a few thousand chapters downloaded from this extension like maybe 4000+
raziel100 commentedon Aug 3, 2026
The 403 error for box novel is easy to fix, but definitely not user friendly or "logical" at all, to fix, open boxnovel using webview, go to the searching box, write anything there and click in search, observe is not to click on the results but in the search button itself, after that it will show you a cloudflare box, conclude it, and it's done, you just need to refresh in the app and everything will show just fine now, for some strange reason this only happens if you try to search something in the app, update the novel to see if new chapters are available or read the Novel itself works just fine
raziel100 commentedon Aug 3, 2026
Guys, could you please tell me if anyone is having issue in the chapter list? For some reason certain novels with 100+ chapters sometimes just don't know the correct sequence, even trying the latest lnreader one is not working, even getting the latest on commit, I just don't know if this is a plug-in issue or a lnreader issue, where should I open a bug report for this? I'm inclined to believe is a plug-in one because it only happens for box novel, and for reference in the website the chapter list is correct, but lnreader don't get the proper order for some reason
torkita commentedon Aug 4, 2026
Yeah i also saw that, some novels are just fetching only 200 or some chapters no matter how many times i refresh, and also, there is a problem of me being unable to update my library, the novels aren't connecting at all with the plugin that are in my library… throwing errors and not updating at all, what the fuck has the owner done with the website…
raziel100 commentedon Aug 4, 2026
Can you reference what novels you have found that fetch only 200 chapters?
torkita commentedon Aug 4, 2026
Wait a few moments i will provide…
torkita commentedon Aug 4, 2026
See it's only grabbing the first page…
torkita commentedon Aug 4, 2026
@raziel100
torkita commentedon Aug 4, 2026
Look at the error, it appears when i try to update the novel saved in my library and somehow it doesn't connects with the extension…
raziel100 commentedon Aug 4, 2026
Yeah. Is also getting only 200 chapters for me too, probably the madara script will need to be updated to get boxnovel properly
D3ICIDE commentedon Aug 4, 2026
@K1ngfish3r the source https://novelnice.com/ has set up its Cloudflare check specifically on the search/listing https://novelnice.com/?s=&post_type=wp-manga endpoint rather than the homepage potentially to block this plugin. While this can be solved by opening the WebView, then manually navigating to search from inside it to trigger and solve the challenge this is not really intuitive or convenient. In the application, BrowseSourceScreen's handleOpenWebView hardcodes url: plugin.site, so there's currently no way for a plugin to tell the webview to open a different URL. Is there some way to fix this issue?
fix(boxnovel): fetch all chapter pages and browse via /read/ to bypas…
feat(multisrc): add Novel Nice as new plugin (boxnovel rebrand)