Troubleshooting

This page is for when you encounter a problem with a source or the app.

What are some common issues?

Failed to bypass Cloudflare

Failed to bypass Cloudflare means that the source you selected has Cloudflare protection on, refer to the Cloudflare guide to fix it. If the solutions provided do not fix the issue, the source has likely raised the Cloudflare protection level high enough that Tachiyomi is not able to access the site.

HTTP error 403

Possible reasons for HTTP error 403:

• The source you selected has Cloudflare protection on, refer to the Cloudflare guide to fix it.
• The source is down, removed the manga, or banned your IP. Open
  public
  WebView to check if this is the case.

HTTP error 404

HTTP error 404 probably means that the source is down or removed the manga. Open

public

WebView to check if this is the case. Migrate to a different source for this manga if you'd like.

HTTP error 429 (Too Many Requests)

HTTP error 429 or Too Many Requests means that the source banned your IP address (in most cases, it's temporary) because you could be downloading or reading too fast. We suggest reporting (opens new window) the issue so that a rate limit can be added to prevent IP bans in the future.

HTTP error 5xx

HTTP error 5xx like 500, 502 and others are server-side errors, and the source you are trying to access has problems on their side. Open the source in

public

WebView and check if the site is down.

HTTP error 1006

HTTP error 1006 means that the source has banned your IP address (in most cases, it's temporary).

HTTP error 1020

HTTP error 1020 means that you have violated a firewall rule the site owner has put up. This usually means that the site owner has raised the Cloudflare protection level or that the site owner is blocking IPs outside their country.

Unable to resolve host / Connection failed / Failed to connect to / timeout / connection reset

Errors like Unable to resolve host, Connection failed, Failed to connect to, timeout, connection reset mean that something is preventing you from connecting to the source.

Possible reasons include:

• Your internet connection is not good enough to connect.
• The app does not have access to the internet.
• Your ISP has blocked the site.
• The site is down.

Try the following solutions to fix this issue:

• Enable
  more_horiz
  More →
  settings
  Settings →
  code
  Advanced → DNS over HTTPS.
• Use a different internet connection (switch to Wi-Fi, a different Wi-Fi network, mobile data or a VPN).
• Reboot your router.

java.security.cert.CertPathValidatorException / Chain validation failed

java.security.cert.CertPathValidatorException or Chain validation failed means there is a problem with validating source's sertificate.

• Check if the site's certificate has expired. Use an online service for checking SSL certificates. If the certificate has expired, wait while the site owner to renew it.
• Ensure that you have the right date and time set on your device.
• Try
  more_horiz
  More →
  settings
  Settings →
  code
  Advanced → Clear cache and Clear cookies.
• Try using a different internet connection (switch to Wi-Fi, a different Wi-Fi network, mobile data or a VPN).
• Try restarting the device.

App not installed

Refer to this section.

Attempt to invoke virtual method 'com.hippo.unifile...

The Attempt to invoke virtual method' com.hippo.unifile... error can be caused by various reasons, but they all have to do with storage.

• Most commonly, it is caused by full storage. Check to see if your device or SD card is full.
• Check if Tachiyomi has access to the SD card. You can enable it in Android settings for app permissions.
• If you're downloading and this error pops up, that means the app might not be able to access the folder you're trying to download to. This may be because the folder is corrupted or does not exist. Use a file manager to check that the folder(s) exist and every folder in the sequence is available and accessible.
• The drive you're writing to is corrupted. Check using a file manager to see if it is accessible.

Cannot Access SD Card

The Cannot Access SD Card error can sometimes be fixed by changing the location of your downloads to somewhere else and back to the SD card, then restarting the app.

Having a file or folder name that is too long can also cause this issue. Android's file manager does not support filenames longer than 255 characters. If you know the file or folder name that is the culprit, you can connect your SD card to your computer and shorten it. Otherwise, delete the Tachiyomi downloads folder off of the SD card.

Storage issues with Android 11+

See this section of the FAQ to learn how Scoped Storage affects Tachiyomi in Android 11+ and how to fix it.

Slow loading

Disclaimer

Tachiyomi is not hosting any content, we are not affiliated with or responsible for any source that is; slow, down, missing chapters, or has subpar image quality.

If any sources are slow, it is likely due to the site being slow, your internet being slow, or a ratelimit applied to the source to reduce load or IP bans.

Reading is laggy

This is usually due to the images in the chapters being too long or large for the reader to handle. If you turn have 32-bit color on, try turning it off under

more_horiz

More →

settings

Settings →

chrome_reader_mode

Reader . This helps sometimes to free up some RAM being used. To eliminate this issue, find a different source that cuts the chapter into more pieces or downscales the images.

If error-specific instructions didn't help or your error isn't on the list, go through Diagnosis.

Diagnosis

• Verify your extensions are up to date (
  explore
  Browse → Extensions, make sure no extensions have an Update button).
• Check if Tachiyomi has an update (
  more_horiz
  More →
  info
  About then tap Check for updates).
• Manually refresh the manga you are having issues with by dragging down.
• Check other manga from the source.
• Verify that WebView is updated.
• Try opening the manga in
  public
  WebView . If there is a Cloudflare protection, wait for it to load. If there is a CAPTCHA, solve it and see if it helped.
• Change your internet connection (switch to Wi-Fi, mobile data or a VPN, use a "What's my IP" site to confirm your IP has changed), then try again.
• Ask other users to try the action that gives you the error.
• Check if the source is either down, or is having issues in a browser.
• Press the retry button in the middle of your manga page if one exists.
• Try the following at
  more_horiz
  More →
  settings
  Settings →
  code
  Advanced
  • Clear Cache
  • Clear Cookies
  • Clear Database
  • DNS over HTTPS
• If your downloads are getting stuck, try deleting the queue and trying again.
• Force close Tachiyomi and reopen it.

An extension update may fix your issue. Wait or check for an extension update if you have not already. There are no ETAs for updates.

If any of these solutions help, go to it only happens to me. If it is not just you, go to everyone is having this problem.

If none of these solutions help, try asking in our Discord Server (opens new window). Check #status-updates first to see if your issue is known. State your app version and the source, manga, and chapter with the problem if it is not listed.

It only happens to me

You may be getting a Cloudflare protection, may have been IP-banned, or encountered some other counter-measure that website owners deploy against programs like Tachiyomi. If that is the case, there is probably nothing that Tachiyomi can do to solve it. Some of them (like Cloudflare) have to be manually solved, and some are temporary (IP bans).

Workarounds that can the lower chance of an issue happening again:

• Don't use downloads with the source.
• Have less manga in your library from the source.

The above are imprecise and fuzzy rules because each site has its non-public limits and triggers.

Everyone is having this problem

If the site is reachable and fully functional, there may be an issue with the extension or app.

1. Have a look at open issues for the app (opens new window) and/or extensions (opens new window).
2. It may have been fixed already but not released yet, so look at closed issues (app (opens new window) / extensions (opens new window)) issues as well.
3. If you can't find the issue there, open a new one.

If the site is not reachable or has issues, all you can do is wait for the site to become functional again.

Solving Cloudflare issues

Cloudflare is an anti-bot mechanism. Some sources intentionally have a higher Cloudflare protection level to block apps like Tachiyomi. You can try the following suggestions to help resolve Cloudflare challenges. If they don't work, migrate to other sources or wait until they lower their protection.

Loading the website in WebView

Try to load the website in WebView. Note that WebView is not the same as using your browser.

How to open WebView

1. Go to
   explore
   Browse in the bottom navbar.
2. Press the source you would like to access.
3. Press the
   public
   WebView icon in the top toolbar.
4. Complete a CAPTCHA if one is shown.
5. Once done, press the X at the top left to return.

You may need to try this multiple times. You can also try pressing the

more_vert

Overflow icon, opening the website in your regular browser, then checking for a CAPTCHA there.

Some sources may have more advanced Cloudflare protection. If you are facing issues, try the following options.

Clearing WebView data

GUIDE

1. In the
   public
   WebView screen, try "Clear cookies" then "Refresh" from the
   more_vert
   Overflow menu.
2. Go to
   more_horiz
   More in the bottom navbar, then
   settings
   Settings →
   code
   Advanced , then select "Clear WebView data".

Changing your user agent

A user agent string helps websites identify information about the requester. While some sources have user agent strings set, most rely on the default value set in the app.

GUIDE

1. Go to
   more_horiz
   More in the bottom navbar, then
   settings
   Settings →
   code
   Advanced .
2. Change the Default user agent string setting to a different one. This website (opens new window) is a decent reference.
3. Restart the app and try accessing the source again.

Update WebView

To update WebView, you need to find what WebView implementation is used on your device. In general, default implementation depends on the Android version as follows:

• Android 10.0 and up - Android System WebView (opens new window).
• Android from 7.0 to 9.0 - Google Chrome (opens new window).
• Android 6.0.1 and below - Android System WebView (opens new window).

Users on Android 7.0 and up can also see and change WebView implementation in Developer Options (opens new window).

Non-standard implementations like Firefox can lead to Tachiyomi not working correctly or, in the worst-case, crash. We recommend to setting your WebView implementation to Android System WebView (opens new window) or Google Chrome (opens new window).

Unable to install the app or extensions

Try installing Split APK Installer (opens new window) from the Google Play Store, then use it to try and install the affected APK. Split APK Installer will tell you why the APK is uninstallable, or it will install the APK for you. Some common errors are listed below.

INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package eu.kanade.tachiyomi signatures do not match the previously installed version; ignoring!

If Split APK Installer outputs the above error when attempting to install the APK, you are likely installing a official build over an existing F-Droid build. The F-Droid build has a different signature than the official build, so you must backup your data, uninstall the app, then restore the data in a fresh install.

DISPLAY_NAME column is null

If Split APK Installer outputs "DISPLAY_NAME column is null", the APK you have downloaded is corrupted. Some users experience this error multiple times after redownloading the APK, so keep redownloading the APK until it installs correctly.

INSTALL_FAILED_NO_MATCHING_ABIS

If Split APK Installer outputs "INSTALL_FAILED_NO_MATCHING_ABIS", the APK you have downloaded is the wrong one for your CPU architecture. Download the correct one or download the universal APK if you are not aware which CPU architecture your device uses.

Getting Logcats and Crash Logs

To dump crash logs following an app crash, go to

more_horiz

More →

settings

Settings →

code

Advanced → Dump crash logs

To get device logs if the app is not behaving as expected, record device logs using a Logcat Reader (opens new window).