Skip to content


Facing issues with a source or the app? Follow these steps to troubleshoot and find solutions.

Primary diagnosis

  1. Update app: Go to dots-verticalThree dots arrow-right-thin Settings arrow-right-thin information-outlineAbout and tap Check for updates.
  2. Manual series refresh: Go to rssFeed and drag down to manually refresh problematic series.
  3. Test other series: Try different series from the same source.
  4. Update WebView: Ensure your WebView is current.
  5. Public WebView: Attempt opening series in public WebView. Solve for CAPTCHA or Cloudflare protection if needed.
  6. Change connection: Switch networks (Wi-Fi, mobile data, VPN) and confirm IP change.
  7. Collaborative check: Get others to replicate the error.
  8. Source status: Verify the source's status in a browser.
  9. Retry button: Look for a retry button on the series page.
  10. Advanced settings: Under dots-verticalThree dots arrow-right-thin Settings arrow-right-thin Data and privacy, try these options:
    • Clear thumbnails cache
    • Clear page cache
    • Clear network cache
    • Clear cookies
    • Under dots-verticalThree dots arrow-right-thin Settings arrow-right-thin Network, try to enable DNS over HTTPS
  11. Download issues: Delete the queue and retry downloads.
  12. Restart Kotatsu: Force close and reopen the app.

If any of these solutions help, go to Personalized Issue. If it is not just you, go to Widespread Issue.

If none of these solutions help, try asking in our Telegram group.

State your app version and the source, series, and chapter with the problem.

An app update may fix your issue

Wait or check for an app update if you have not already. There are no ETAs for updates.

Personalized issue

If you're the only one facing a problem, you might be encountering an IP ban, or other countermeasures set by website owners against programs like Kotatsu.

To minimize future issues:

  • Avoid using downloads with the source.
  • Reduce the number of series in your favourites/history from that source.


These are general guidelines as each site has its specific undisclosed limits and triggers.

Widespread issue

When everyone experiences a problem, it could be with the source or app:

  1. Check open issues for the app and/or parsers.
  2. Check closed issues (app/parsers) in case it's resolved but not yet released.
  3. If not found, create a new issue.


If the site itself is problematic, patience is the only solution until it becomes functional again.