Access denied 403

[Khubi1412]

Brief summary

It is continuously showing access denied 403. It needs to be solved

Steps to reproduce

No response

Kotatsu version

9.2

Android version

15

Device

OnePlus 12

Acknowledgements

• This is not a duplicate of an existing issue. Please look through the list of open issues before creating a new one.
• This is not an issue with a specific manga source. Otherwise, you have to open an issue in the parsers repository.

[anny-moose]

Happens to me too when trying to read anything from the MangaFire English source.

[AlphaKnight1829]

Same with mangafire source . The site itself is ok . The app is the problem

[AlphaKnight1829]

Mangafire did an update on there site . So kotatsu need to update theres to accommodate the new mangafire source

[MariusAlbrecht]

Provide steps to reproduce.
If this is source specific (which is very likely imo) then this is also the wrong place for your issue.

This is also, very obviously so, a duplicate issue.

[bonwilliam]

Issue was present in version 9.2, fixed with version n 9.3 but now it's back with version 9.4.

Step to reproduce :

• open mangafire source
• open any manga / webtoon
• swipe down to refresh chapters, you get an error 403

[AlphaKnight1829]

So what wait again for several weeks to get it fixed ? This is getting frustrating.

…

On Sun, 2 Nov 2025, 4:45 pm Bill, ***@***.***> wrote: *bonwilliam* left a comment (KotatsuApp/Kotatsu#1668) <#1668 (comment)> Issue was present in versions n 9.2, fixed with versions n 9.3 but now it's back with version 9.4. Step to reproduce : - open mangafire source - open any manga / webtoon - swipe down to refresh chapters, you get an error 403 — Reply to this email directly, view it on GitHub <#1668 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYPWIZ7YN76WHE6QR4JZFNL32XAEFAVCNFSM6AAAAACJEMGGSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINZXGY2TKMJUGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[bonwilliam]

So what wait again for several weeks to get it fixed ? This is getting
frustrating.
…

You can maybe also downgrade the application with adb If it works, didn't try it yet though.

Being software engineering, I know that bugs can be frustrating for developper and customer as well, but since this application is already free, we can already say thank you to the developpers for their work. Despite the few bugs that can impact us from time to time, this application is great

Edit : just tried downgrading the application, even removed the saved data, and mangafire still gives 403, so it's most probably not a regression of the application but a change in mangafire. But it's indeed strange that it happened at the same day the kotatsu 9.4 was published.

[AlphaKnight1829]

So what wait again for several weeks to get it fixed ? This is getting
frustrating.
…

You can maybe also downgrade the application with adb If it works, didn't try it yet though.

Being software engineering, I know that bugs can be frustrating for developper and customer as well, but since this application is already free, we can already say thank you to the developpers for their work. Despite the few bugs that can impact us from time to time, this application is great

Edit : just tried downgrading the application, even removed the saved data, and mangafire still gives 403, so it's most probably not a regression of the application but a change in mangafire. But it's indeed strange that it happened at the same day the kotatsu 9.4 was published.

Did mangafire did some update ? I jsut went there the day the bug happened. Did'nt notice anything new

[bonwilliam]

So what wait again for several weeks to get it fixed ? This is getting
frustrating.
…

You can maybe also downgrade the application with adb If it works, didn't try it yet though.
Being software engineering, I know that bugs can be frustrating for developper and customer as well, but since this application is already free, we can already say thank you to the developpers for their work. Despite the few bugs that can impact us from time to time, this application is great
Edit : just tried downgrading the application, even removed the saved data, and mangafire still gives 403, so it's most probably not a regression of the application but a change in mangafire. But it's indeed strange that it happened at the same day the kotatsu 9.4 was published.

Did mangafire did some update ? I jsut went there the day the bug happened. Did'nt notice anything new

I assume that something changed indeed, meanwhile I started migrating my mangas to new source.

[AlphaKnight1829]

9.4.1 still problem not fixed with mangafire source just checked it today

…

On Tue, 4 Nov 2025, 12:50 am Bill, ***@***.***> wrote: *bonwilliam* left a comment (KotatsuApp/Kotatsu#1668) <#1668 (comment)> So what wait again for several weeks to get it fixed ? This is getting frustrating. … <#m_-4287653112733689695_> You can maybe also downgrade the application with adb If it works, didn't try it yet though. Being software engineering, I know that bugs can be frustrating for developper and customer as well, but since this application is already free, we can already say thank you to the developpers for their work. Despite the few bugs that can impact us from time to time, this application is great Edit : just tried downgrading the application, even removed the saved data, and mangafire still gives 403, so it's most probably not a regression of the application but a change in mangafire. But it's indeed strange that it happened at the same day the kotatsu 9.4 was published. Did mangafire did some update ? I jsut went there the day the bug happened. Did'nt notice anything new I assume that something changed indeed, meanwhile I started migrating my mangas to new source. — Reply to this email directly, view it on GitHub <#1668 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYPWIZ74BQT37XC6HJIN4KD326BWJAVCNFSM6AAAAACJEMGGSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOBRGUYTOMBRGY> . You are receiving this because you commented.Message ID: ***@***.***>