[knoxtspace] ERROR 403 FORBIDDEN access

[amethysteria]

Plugin

English: KnoxT

Severity

Can't Load Novels

Steps To Reproduce

1. Open the plugin
2. The error appears

Expected Behavior

"The plugin should have loaded the novels "

Actual Behavior

"An error message appeared saying error 403 unable to reach website try webview which i did and on the webview page it showed 403 FORBIDDEN ( request forbidden by administrative rules)"

LNReader Version

2.1.3

Plugin Version

1.1.10

Android Version

Android 15

Other Details

Acknowledgements

• I have searched existing issues and confirmed this is not a duplicate.
• I have written a clear and descriptive title.
• I have updated the app to the latest version 2.0.0.
• I have updated all installed plugins to the latest version.
• I understand that app-specific issues should be reported in the app repository.

[torkita]

@amethysteria in my app the domain is acting fine, can you check again if it is happening again?

[RibatTRW]

Independently checked this from a second location: the plugin works end to end here - popularNovels returns 20 novels from https://knoxt.space/series/?page=1, searchNovels works, a novel parses with its chapters, and parseChapter returns the full text. That was verified both with the repo's live check and by driving the plugin in the plugin playground. The site answered HTTP 200 for every path the plugin requests, with a plain User-Agent, a mobile browser User-Agent, and no User-Agent at all, so nothing about the plugin's request shape looks blocked.

Since the app's webview - a real browser - also returned 403 FORBIDDEN (request forbidden by administrative rules), that reads like the host's firewall refusing your network rather than a plugin problem, and no plugin change can work around a block enforced at the server.

If it is still happening, it would help to know which exact URL fails, whether it works over a different network such as mobile data or a VPN, and your country/ISP - if an IP range is blocked, only the site's admin can lift it.

[SupremeMango]

This issue could be because Cloudflare's web application firewall, maybe you could use a vpn?