Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Tachidesk-Docker Support Thread

Featured Replies

On 10/30/2025 at 1:32 PM, zinkpro45 said:

Seemingly having an issue with this where it just doesn't check for new issues automatically. Has anyone else ran into this? I'm only using the Weeb Central extension as a source. Going to a manga and clicking update manually grabs everything new, but then it just won't check automatically after that.

Disregard, didn't know that "Skip Updating Entries" blocks this. I had to update the setting to be something closer to this:
image.png

  • 1 month later...
  • Replies 85
  • Views 33.7k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • New Way to get Rid of the File permission error.   I Don't know if this will stick, or if it will get added in the default container. Create a Backup before adding or removing these Cha

  • I didn't think that Dockers work that way but apparently they do.   For volume mapping the unraid host uses the -v command which adds the problem discussed bellow:     Accordi

  • theangelofspace15
    theangelofspace15

    Well, i didnt see any comment lol but in case anyone eant to give ot a try this os how it looks. `Config` is your config file, `/config/download` the folder the app downloads manga, `config/local` you

Posted Images

On 10/19/2025 at 4:54 AM, C3004 said:

Hi coresplinter,

Was the backup created by the ghcr.io/suwayomi/tachidesk:v2.1.1930 preview version?

Hey Sorry!
Forgot to get back to you and I've been allowing it to auto update since. I was on the latest update version back then and now I'm

Server - v2.1.2031

Thank you for offerring to help!

  • 1 month later...

Hi I'm trying to enable tailscale with suwayomi, following the instructions here: https://docs.unraid.net/unraid-os/system-administration/secure-your-server/tailscale/#adding-tailscale-to-docker-containers

However I keep getting:

ERROR: No root privileges!

ERROR: Unraid Docker Hook script throw an error!

During startup of the container. I got the app from the community store and I asked the discord server for tachidesk and it said that it shouldn't need root privileges. I tried with it anyway and it still doesn't work. Otherwise, the settings are pretty normal, no exit nodes other than the default. And I was able to get other containers to work with tailscale so this is a little confusing to me.

  • 4 weeks later...

Hi Everyone,
I am encountering a fatal JVM crash when running Tachidesk in Docker on an Unraid server. The container aborts with the following error:
#

# A fatal error has been detected by the Java Runtime Environment:

#

# SIGILL (0x4) at pc=0x0000147591d271fa, pid=95, tid=255

#

# JRE version: OpenJDK Runtime Environment Temurin-25.0.1+8 (25.0.1+8) (build 25.0.1+8-LTS)

# Java VM: OpenJDK 64-Bit Server VM Temurin-25.0.1+8 (25.0.1+8-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)

# Problematic frame:

# C [libcef.so+0x76371fa]

#

# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

#

# An error report file with more information is saved as:

# /home/suwayomi/hs_err_pid95.log

#

# If you would like to submit a bug report, please visit:

# https://github.com/adoptium/adoptium-support/issues

#

Aborted
The crash seems to originate from libcef.so, and the JVM terminates with SIGILL (Illegal Instruction).

is there any workaround on the issue

  • 3 months later...
On 1/18/2026 at 11:07 PM, kazuuuu said:

Hi I'm trying to enable tailscale with suwayomi, following the instructions here: https://docs.unraid.net/unraid-os/system-administration/secure-your-server/tailscale/#adding-tailscale-to-docker-containers

However I keep getting:

ERROR: No root privileges!

ERROR: Unraid Docker Hook script throw an error!

During startup of the container. I got the app from the community store and I asked the discord server for tachidesk and it said that it shouldn't need root privileges. I tried with it anyway and it still doesn't work. Otherwise, the settings are pretty normal, no exit nodes other than the default. And I was able to get other containers to work with tailscale so this is a little confusing to me.

I also would like to know how to run tailscale on this container so that i can connect to it from outside of my network.

i am able to get it working by setting "-u 0:0" in extra parameters instead of "-u 99:100" but im not so sure that is intended.

for now i just tailscale into the server itself instead of the specific container which seems to work.

  • 3 weeks later...

I have installed the Tachidesk-Docker docker image on my Unraid 6.12 server using the Repository ghcr.io/suwayomi/suwayomi-server:latest that uses the default bridge network type. I also have a Flaresoverr docker image that Tachideks-Docker is configured to use with a URL that points to the exposed IP and port on the server. When I access the flaresolver docker via the configured IP and port in my browser, I get the following output:

{"msg": "FlareSolverr is ready!", "version": "3.5.0", "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36"}

The Tachidesk-Docker container is able to start up and I am able to connect to the webui and setup the standard extension repositories:

- https://raw.githubusercontent.com/suwayomi/tachiyomi-extension/repo/index.min.json

- https://github.com/keiyoushi/extensions/blob/repo/index.min.json

I have installed several extensions, and only the MangaFox extension is allowing me to browse manga. The other extensions that I have installed like Mangakakalot is displaying the following error in the browse window:

Unable to load data
Failed to connect to www.mangakakalot.gg/0.0.0.0:443

I can load the website and view the Suwayomi web view. When I look into the logs, the following is the error that is thrown by the server:

2026-06-26 10:36:34.919 [DefaultDispatcher-worker-2] ERROR suwayomi.tachidesk.graphql.AsDataFetcherResult - asDataFetcherResult: failed due to
java.net.ConnectException: Failed to connect to www.mangakakalot.gg/0.0.0.0:443
        at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:278)
        at okhttp3.internal.connection.ConnectPlan.connectTcp(ConnectPlan.kt:135)
        at okhttp3.internal.connection.FastFallbackExchangeFinder$launchTcpConnect$1.runOnce(FastFallbackExchangeFinder.kt:141)
        at okhttp3.internal.concurrent.TaskRunner$runnable$1.run(TaskRunner.kt:81)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
        at java.base/sun.nio.ch.Net.pollConnect(Native Method)
        at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)
        at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(Unknown Source)
        at java.base/sun.nio.ch.NioSocketImpl.connect(Unknown Source)
        at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
        at java.base/java.net.Socket.connect(Unknown Source)
        at okhttp3.internal.platform.Platform.connectSocket(Platform.kt:148)
        at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:276)
        ... 6 common frames omitted

I have Suwayomi installed on my windows machine and I can use all of these extensions that are not working in Tachidesk-Docker. Just wanted to see if anyone else has gotten this error and found a way to resolve it. I tried querying google and I have tried the following things with no success:

- Adding a docker container dns with --dns 1.1.1.1 in the extra parameters field.

- Change the Network Type to Host instead of Bridge. When I did this I got a "Unable to load data Unsupported or unrecognized SSL message" error instead. Not sure if that is progress.

I also do not have PiHole or AdGuard installed, but I do have tailscale installed. Tailscale is the base install with no services or apps defined.

Edited by bubdub

  • Author
3 hours ago, bubdub said:

I have installed the Tachidesk-Docker docker image on my Unraid 6.12 server using the Repository ghcr.io/suwayomi/suwayomi-server:latest that uses the default bridge network type. I also have a Flaresoverr docker image that Tachideks-Docker is configured to use with a URL that points to the exposed IP and port on the server. When I access the flaresolver docker via the configured IP and port in my browser, I get the following output:

{"msg": "FlareSolverr is ready!", "version": "3.5.0", "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36"}

The Tachidesk-Docker container is able to start up and I am able to connect to the webui and setup the standard extension repositories:

- https://raw.githubusercontent.com/suwayomi/tachiyomi-extension/repo/index.min.json

- https://github.com/keiyoushi/extensions/blob/repo/index.min.json

I have installed several extensions, and only the MangaFox extension is allowing me to browse manga. The other extensions that I have installed like Mangakakalot is displaying the following error in the browse window:

Unable to load data
Failed to connect to www.mangakakalot.gg/0.0.0.0:443

I can load the website and view the Suwayomi web view. When I look into the logs, the following is the error that is thrown by the server:

2026-06-26 10:36:34.919 [DefaultDispatcher-worker-2] ERROR suwayomi.tachidesk.graphql.AsDataFetcherResult - asDataFetcherResult: failed due to
java.net.ConnectException: Failed to connect to www.mangakakalot.gg/0.0.0.0:443
        at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:278)
        at okhttp3.internal.connection.ConnectPlan.connectTcp(ConnectPlan.kt:135)
        at okhttp3.internal.connection.FastFallbackExchangeFinder$launchTcpConnect$1.runOnce(FastFallbackExchangeFinder.kt:141)
        at okhttp3.internal.concurrent.TaskRunner$runnable$1.run(TaskRunner.kt:81)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
        at java.base/sun.nio.ch.Net.pollConnect(Native Method)
        at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)
        at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(Unknown Source)
        at java.base/sun.nio.ch.NioSocketImpl.connect(Unknown Source)
        at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
        at java.base/java.net.Socket.connect(Unknown Source)
        at okhttp3.internal.platform.Platform.connectSocket(Platform.kt:148)
        at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:276)
        ... 6 common frames omitted

I have Suwayomi installed on my windows machine and I can use all of these extensions that are not working in Tachidesk-Docker. Just wanted to see if anyone else has gotten this error and found a way to resolve it. I tried querying google and I have tried the following things with no success:

- Adding a docker container dns with --dns 1.1.1.1 in the extra parameters field.

- Change the Network Type to Host instead of Bridge. When I did this I got a "Unable to load data Unsupported or unrecognized SSL message" error instead. Not sure if that is progress.

I also do not have PiHole or AdGuard installed, but I do have tailscale installed. Tailscale is the base install with no services or apps defined.

Hi!

Having tested mangakakalot on my instance flaresolver must work or the site can't be accessed.

My flaresolver log is:

grafik.png

In what network mode is your flaresolver and tachidesk container?

It seems you only got a response from flaresolver when you had the tachidesk container in the host network mode, so it was using the host unraid network stack, which means the requests went through your home network, which can lead to many issues. (Ports you map in docker edit are mapped from the internal docker network to your servers ip adress. Only containers in host mode can access other containers this way)

For better communication we want the containers in the same network stack. We can either use the base unraid bridge network and use the container ip's (set according to container startup; ip needs to be locked otherwise it changes almost every time) or we use a user defined docker network, in which the container name is the container hostname and can be used instead of the ip.

I don't want to bother with the standard docker bridge so here is the setup for the user defined bridge:

  • create bridge in unraid console: docker network create manga

  • edit flaresolver container, set network type to custom: manga

  • edit tachidesk container, set network to custom: manga

  • scroll down to show more settings; set allow flaresolver_enabled to true; set flaresolverr_url to http://FLARESOLVERRCONTAINERNAME:8191

    grafik.png

Try this. If it doesn't work please share the flaresolver logs too.

Kind Regards

Thanks for responding and checking your instance.

In what network mode is your flaresolver and tachidesk container?

My original install had both the flaresolverr and tachidesk containers in bridge network mode. As per your suggestion I have setup a custom network manga and configured the flaresolverr and tachidesk to have a network mode of "Custom: Manga". Even with this change, I am still having the 0.0.0.0:443 error for Mangakakalot but no issues with Mangafox. I am using the flaresolverr Official container from the Apps directory.

I tried to do some debugging with help of Gemini:

  1. Verified that the flaresolverr instance was working by browsing to the server ip address and port. Got a "Flaresolverr is ready" msg in the JSON response. This indicates that flaresolverr is working.

  2. I used the curl command "curl -X POST http://flaresolverr:8191/v1 -H "Content-Type: application/json" -d '{"cmd": "request.get", "url": "https://www.mangakakalot.com", "maxTimeout": 60000}'" from the console of my Tachidesk instance to verify the container can connect. I see a proper webpage.

  3. I then configured flaresolver url to "http://flaresolverr:8191" in the tachidesk container, restarted and got the following in the logs:

Tachidesk Log:

16:47:58.901 [DefaultDispatcher-worker-1] DEBUG suwayomi.tachidesk.manga.impl.util.PackageTools -- loading jar with path: /home/suwayomi/.local/share/Tachidesk/extensions/tachiyomi-en.mangakakalot-v1.4.21.jar
16:47:59.048 [DefaultDispatcher-worker-1] ERROR suwayomi.tachidesk.graphql.AsDataFetcherResult -- asDataFetcherResult: failed due to
java.net.ConnectException: Failed to connect to www.mangakakalot.gg/0.0.0.0:443
        at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:278)
        at okhttp3.internal.connection.ConnectPlan.connectTcp(ConnectPlan.kt:135)
        at okhttp3.internal.connection.FastFallbackExchangeFinder$launchTcpConnect$1.runOnce(FastFallbackExchangeFinder.kt:141)
        at okhttp3.internal.concurrent.TaskRunner$runnable$1.run(TaskRunner.kt:81)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
        at java.base/sun.nio.ch.Net.pollConnect(Native Method)
        at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)
        at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(Unknown Source)
        at java.base/sun.nio.ch.NioSocketImpl.connect(Unknown Source)
        at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
        at java.base/java.net.Socket.connect(Unknown Source)
        at okhttp3.internal.platform.Platform.connectSocket(Platform.kt:148)
        at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:276)
        ... 6 common frames omitted

Flaresolverr Log (Note:when I browsed Mangakakalot in the webui there was not change in output almost like tachidesk did not access it):

2026-06-27 20:45:25 INFO     ReqId 22780464257920 FlareSolverr 3.5.0
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Debug log enabled
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Testing web browser installation...
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Platform: Linux-6.1.126-Unraid-x86_64-with-glibc2.36
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Chrome / Chromium path: /usr/bin/chromium
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Chrome / Chromium major version: 148
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Launching web browser...
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Launching web browser...
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Skipping Selenium Manager; path to chrome driver specified in Service class: /app/chromedriver
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Started executable: `/app/chromedriver` in a child process with pid: 34 using 0 to output -3
2026-06-27 20:45:27 INFO     ReqId 22780464257920 FlareSolverr User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36
2026-06-27 20:45:27 INFO     ReqId 22780464257920 Test successful!
2026-06-27 20:45:27 INFO     ReqId 22780464257920 Serving on http://0.0.0.0:8191
  1. I tried curl to mangakakalot.gg instead mangakakalot.com as I noticed that is the url mentioned in the extension. When I run the command "curl -X POST http://flaresolverr:8191/v1 -H "Content-Type: application/json" -d '{"cmd": "request.get", "url": "https://mangakakalot.gg", "maxTimeout": 60000}'" I get the following output on the command line:

{"status": "error", "message": "Error: Error solving the challenge. Message: unknown error: net::ERR_CONNECTION_REFUSED\\n  (Session info: chrome=148.0.7778.178)\\nStacktrace:\\n#0 0x556cde27fcfe <unknown>\\n#1 0x556cddc0ff34 <unknown>\\n#2 0x556cddc0ced4 <unknown>\\n#3 0x556cddbf7c35 <unknown>\\n#4 0x556cddbf9833 <unknown>\\n#5 0x556cddbf7f82 <unknown>\\n#6 0x556cddbf77e1 <unknown>\\n#7 0x556cddbf7739 <unknown>\\n#8 0x556cddbf5b4a <unknown>\\n#9 0x556cddbf5e7a <unknown>\\n#10 0x556cddc13fea <unknown>\\n#11 0x556cddca8b64 <unknown>\\n#12 0x556cddc85f12 <unknown>\\n#13 0x556cddca857f <unknown>\\n#14 0x556cddc85cd3 <unknown>\\n#15 0x556cddc52b8e <unknown>\\n#16 0x556cddc537b1 <unknown>\\n#17 0x556cde2424e0 <unknown>\\n#18 0x556cde2457a5 <unknown>\\n#19 0x556cde2451da <unknown>\\n#20 0x556cde245c05 <unknown>\\n#21 0x556cde231f29 <unknown>\\n#22 0x556cde245f67 <unknown>\\n#23 0x556cde21a426 <unknown>\\n#24 0x556cde26c5f5 <unknown>\\n#25 0x556cde26c7d3 <unknown>\\n#26 0x556cde27e86a <unknown>\\n#27 0x151ad28ad1f5 <unknown>\\n", "startTimestamp": 1782593500184, "endTimestamp": 1782593504440, "version": "3.5.0"}

and the following output in filesolverr log:

2026-06-27 20:45:25 INFO     ReqId 22780464257920 FlareSolverr 3.5.0
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Debug log enabled
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Testing web browser installation...
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Platform: Linux-6.1.126-Unraid-x86_64-with-glibc2.36
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Chrome / Chromium path: /usr/bin/chromium
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Chrome / Chromium major version: 148
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Launching web browser...
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Launching web browser...
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Skipping Selenium Manager; path to chrome driver specified in Service class: /app/chromedriver
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Started executable: `/app/chromedriver` in a child process with pid: 34 using 0 to output -3
2026-06-27 20:45:27 INFO     ReqId 22780464257920 FlareSolverr User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36
2026-06-27 20:45:27 INFO     ReqId 22780464257920 Test successful!
2026-06-27 20:45:27 INFO     ReqId 22780464257920 Serving on http://0.0.0.0:8191
2026-06-27 20:51:40 INFO     ReqId 22780426540736 Incoming request => POST /v1 body: {'cmd': 'request.get', 'url': 'https://mangakakalot.gg', 'maxTimeout': 60000}
2026-06-27 20:51:40 DEBUG    ReqId 22780426540736 Launching web browser...
2026-06-27 20:51:40 DEBUG    ReqId 22780426540736 Skipping Selenium Manager; path to chrome driver specified in Service class: /app/chromedriver
2026-06-27 20:51:40 DEBUG    ReqId 22780426540736 Started executable: `/app/chromedriver` in a child process with pid: 157 using 0 to output -3
2026-06-27 20:51:40 DEBUG    ReqId 22780426540736 New instance of webdriver has been created to perform the request
2026-06-27 20:51:40 DEBUG    ReqId 22780418135744 Navigating to... https://mangakakalot.gg
2026-06-27 20:51:44 DEBUG    ReqId 22780426540736 A used instance of webdriver has been destroyed
2026-06-27 20:51:44 ERROR    ReqId 22780426540736 Error: Error solving the challenge. Message: unknown error: net::ERR_CONNECTION_REFUSED\n  (Session info: chrome=148.0.7778.178)\nStacktrace:\n#0 0x556cde27fcfe <unknown>\n#1 0x556cddc0ff34 <unknown>\n#2 0x556cddc0ced4 <unknown>\n#3 0x556cddbf7c35 <unknown>\n#4 0x556cddbf9833 <unknown>\n#5 0x556cddbf7f82 <unknown>\n#6 0x556cddbf77e1 <unknown>\n#7 0x556cddbf7739 <unknown>\n#8 0x556cddbf5b4a <unknown>\n#9 0x556cddbf5e7a <unknown>\n#10 0x556cddc13fea <unknown>\n#11 0x556cddca8b64 <unknown>\n#12 0x556cddc85f12 <unknown>\n#13 0x556cddca857f <unknown>\n#14 0x556cddc85cd3 <unknown>\n#15 0x556cddc52b8e <unknown>\n#16 0x556cddc537b1 <unknown>\n#17 0x556cde2424e0 <unknown>\n#18 0x556cde2457a5 <unknown>\n#19 0x556cde2451da <unknown>\n#20 0x556cde245c05 <unknown>\n#21 0x556cde231f29 <unknown>\n#22 0x556cde245f67 <unknown>\n#23 0x556cde21a426 <unknown>\n#24 0x556cde26c5f5 <unknown>\n#25 0x556cde26c7d3 <unknown>\n#26 0x556cde27e86a <unknown>\n#27 0x151ad28ad1f5 <unknown>\n
2026-06-27 20:51:44 DEBUG    ReqId 22780426540736 Response => POST /v1 body: {'status': 'error', 'message': 'Error: Error solving the challenge. Message: unknown error: net::ERR_CONNECTION_REFUSED\\n  (Session info: chrome=148.0.7778.178)\\nStacktrace:\\n#0 0x556cde27fcfe <unknown>\\n#1 0x556cddc0ff34 <unknown>\\n#2 0x556cddc0ced4 <unknown>\\n#3 0x556cddbf7c35 <unknown>\\n#4 0x556cddbf9833 <unknown>\\n#5 0x556cddbf7f82 <unknown>\\n#6 0x556cddbf77e1 <unknown>\\n#7 0x556cddbf7739 <unknown>\\n#8 0x556cddbf5b4a <unknown>\\n#9 0x556cddbf5e7a <unknown>\\n#10 0x556cddc13fea <unknown>\\n#11 0x556cddca8b64 <unknown>\\n#12 0x556cddc85f12 <unknown>\\n#13 0x556cddca857f <unknown>\\n#14 0x556cddc85cd3 <unknown>\\n#15 0x556cddc52b8e <unknown>\\n#16 0x556cddc537b1 <unknown>\\n#17 0x556cde2424e0 <unknown>\\n#18 0x556cde2457a5 <unknown>\\n#19 0x556cde2451da <unknown>\\n#20 0x556cde245c05 <unknown>\\n#21 0x556cde231f29 <unknown>\\n#22 0x556cde245f67 <unknown>\\n#23 0x556cde21a426 <unknown>\\n#24 0x556cde26c5f5 <unknown>\\n#25 0x556cde26c7d3 <unknown>\\n#26 0x556cde27e86a <unknown>\\n#27 0x151ad28ad1f5 <unknown>\\n', 'startTimestamp': 1782593500184, 'endTimestamp': 1782593504440, 'version': '3.5.0'}
2026-06-27 20:51:44 INFO     ReqId 22780426540736 Response in 4.256 s
2026-06-27 20:51:44 INFO     ReqId 22780426540736 172.19.0.3 POST http://flaresolverr:8191/v1 500 Internal Server Error

This is making me feel like my tachidesk install is not making a proper request to the filesolverr instance. I double checked the filesolverr url and it looks right with the value "http://flaresolverr:8191".

Please let me know if need anything else from me. Your assistance is greatly appreciated.

  • Author
On 6/27/2026 at 10:58 PM, bubdub said:

Thanks for responding and checking your instance.

My original install had both the flaresolverr and tachidesk containers in bridge network mode. As per your suggestion I have setup a custom network manga and configured the flaresolverr and tachidesk to have a network mode of "Custom: Manga". Even with this change, I am still having the 0.0.0.0:443 error for Mangakakalot but no issues with Mangafox. I am using the flaresolverr Official container from the Apps directory.

I tried to do some debugging with help of Gemini:

  1. Verified that the flaresolverr instance was working by browsing to the server ip address and port. Got a "Flaresolverr is ready" msg in the JSON response. This indicates that flaresolverr is working.

  2. I used the curl command "curl -X POST http://flaresolverr:8191/v1 -H "Content-Type: application/json" -d '{"cmd": "request.get", "url": "https://www.mangakakalot.com", "maxTimeout": 60000}'" from the console of my Tachidesk instance to verify the container can connect. I see a proper webpage.

  3. I then configured flaresolver url to "http://flaresolverr:8191" in the tachidesk container, restarted and got the following in the logs:

Tachidesk Log:

16:47:58.901 [DefaultDispatcher-worker-1] DEBUG suwayomi.tachidesk.manga.impl.util.PackageTools -- loading jar with path: /home/suwayomi/.local/share/Tachidesk/extensions/tachiyomi-en.mangakakalot-v1.4.21.jar
16:47:59.048 [DefaultDispatcher-worker-1] ERROR suwayomi.tachidesk.graphql.AsDataFetcherResult -- asDataFetcherResult: failed due to
java.net.ConnectException: Failed to connect to www.mangakakalot.gg/0.0.0.0:443
        at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:278)
        at okhttp3.internal.connection.ConnectPlan.connectTcp(ConnectPlan.kt:135)
        at okhttp3.internal.connection.FastFallbackExchangeFinder$launchTcpConnect$1.runOnce(FastFallbackExchangeFinder.kt:141)
        at okhttp3.internal.concurrent.TaskRunner$runnable$1.run(TaskRunner.kt:81)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
        at java.base/sun.nio.ch.Net.pollConnect(Native Method)
        at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)
        at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(Unknown Source)
        at java.base/sun.nio.ch.NioSocketImpl.connect(Unknown Source)
        at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
        at java.base/java.net.Socket.connect(Unknown Source)
        at okhttp3.internal.platform.Platform.connectSocket(Platform.kt:148)
        at okhttp3.internal.connection.ConnectPlan.connectSocket(ConnectPlan.kt:276)
        ... 6 common frames omitted

Flaresolverr Log (Note:when I browsed Mangakakalot in the webui there was not change in output almost like tachidesk did not access it):

2026-06-27 20:45:25 INFO     ReqId 22780464257920 FlareSolverr 3.5.0
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Debug log enabled
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Testing web browser installation...
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Platform: Linux-6.1.126-Unraid-x86_64-with-glibc2.36
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Chrome / Chromium path: /usr/bin/chromium
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Chrome / Chromium major version: 148
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Launching web browser...
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Launching web browser...
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Skipping Selenium Manager; path to chrome driver specified in Service class: /app/chromedriver
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Started executable: `/app/chromedriver` in a child process with pid: 34 using 0 to output -3
2026-06-27 20:45:27 INFO     ReqId 22780464257920 FlareSolverr User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36
2026-06-27 20:45:27 INFO     ReqId 22780464257920 Test successful!
2026-06-27 20:45:27 INFO     ReqId 22780464257920 Serving on http://0.0.0.0:8191
  1. I tried curl to mangakakalot.gg instead mangakakalot.com as I noticed that is the url mentioned in the extension. When I run the command "curl -X POST http://flaresolverr:8191/v1 -H "Content-Type: application/json" -d '{"cmd": "request.get", "url": "https://mangakakalot.gg", "maxTimeout": 60000}'" I get the following output on the command line:

{"status": "error", "message": "Error: Error solving the challenge. Message: unknown error: net::ERR_CONNECTION_REFUSED\\n  (Session info: chrome=148.0.7778.178)\\nStacktrace:\\n#0 0x556cde27fcfe <unknown>\\n#1 0x556cddc0ff34 <unknown>\\n#2 0x556cddc0ced4 <unknown>\\n#3 0x556cddbf7c35 <unknown>\\n#4 0x556cddbf9833 <unknown>\\n#5 0x556cddbf7f82 <unknown>\\n#6 0x556cddbf77e1 <unknown>\\n#7 0x556cddbf7739 <unknown>\\n#8 0x556cddbf5b4a <unknown>\\n#9 0x556cddbf5e7a <unknown>\\n#10 0x556cddc13fea <unknown>\\n#11 0x556cddca8b64 <unknown>\\n#12 0x556cddc85f12 <unknown>\\n#13 0x556cddca857f <unknown>\\n#14 0x556cddc85cd3 <unknown>\\n#15 0x556cddc52b8e <unknown>\\n#16 0x556cddc537b1 <unknown>\\n#17 0x556cde2424e0 <unknown>\\n#18 0x556cde2457a5 <unknown>\\n#19 0x556cde2451da <unknown>\\n#20 0x556cde245c05 <unknown>\\n#21 0x556cde231f29 <unknown>\\n#22 0x556cde245f67 <unknown>\\n#23 0x556cde21a426 <unknown>\\n#24 0x556cde26c5f5 <unknown>\\n#25 0x556cde26c7d3 <unknown>\\n#26 0x556cde27e86a <unknown>\\n#27 0x151ad28ad1f5 <unknown>\\n", "startTimestamp": 1782593500184, "endTimestamp": 1782593504440, "version": "3.5.0"}

and the following output in filesolverr log:

2026-06-27 20:45:25 INFO     ReqId 22780464257920 FlareSolverr 3.5.0
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Debug log enabled
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Testing web browser installation...
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Platform: Linux-6.1.126-Unraid-x86_64-with-glibc2.36
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Chrome / Chromium path: /usr/bin/chromium
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Chrome / Chromium major version: 148
2026-06-27 20:45:25 INFO     ReqId 22780464257920 Launching web browser...
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Launching web browser...
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Skipping Selenium Manager; path to chrome driver specified in Service class: /app/chromedriver
2026-06-27 20:45:25 DEBUG    ReqId 22780464257920 Started executable: `/app/chromedriver` in a child process with pid: 34 using 0 to output -3
2026-06-27 20:45:27 INFO     ReqId 22780464257920 FlareSolverr User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36
2026-06-27 20:45:27 INFO     ReqId 22780464257920 Test successful!
2026-06-27 20:45:27 INFO     ReqId 22780464257920 Serving on http://0.0.0.0:8191
2026-06-27 20:51:40 INFO     ReqId 22780426540736 Incoming request => POST /v1 body: {'cmd': 'request.get', 'url': 'https://mangakakalot.gg', 'maxTimeout': 60000}
2026-06-27 20:51:40 DEBUG    ReqId 22780426540736 Launching web browser...
2026-06-27 20:51:40 DEBUG    ReqId 22780426540736 Skipping Selenium Manager; path to chrome driver specified in Service class: /app/chromedriver
2026-06-27 20:51:40 DEBUG    ReqId 22780426540736 Started executable: `/app/chromedriver` in a child process with pid: 157 using 0 to output -3
2026-06-27 20:51:40 DEBUG    ReqId 22780426540736 New instance of webdriver has been created to perform the request
2026-06-27 20:51:40 DEBUG    ReqId 22780418135744 Navigating to... https://mangakakalot.gg
2026-06-27 20:51:44 DEBUG    ReqId 22780426540736 A used instance of webdriver has been destroyed
2026-06-27 20:51:44 ERROR    ReqId 22780426540736 Error: Error solving the challenge. Message: unknown error: net::ERR_CONNECTION_REFUSED\n  (Session info: chrome=148.0.7778.178)\nStacktrace:\n#0 0x556cde27fcfe <unknown>\n#1 0x556cddc0ff34 <unknown>\n#2 0x556cddc0ced4 <unknown>\n#3 0x556cddbf7c35 <unknown>\n#4 0x556cddbf9833 <unknown>\n#5 0x556cddbf7f82 <unknown>\n#6 0x556cddbf77e1 <unknown>\n#7 0x556cddbf7739 <unknown>\n#8 0x556cddbf5b4a <unknown>\n#9 0x556cddbf5e7a <unknown>\n#10 0x556cddc13fea <unknown>\n#11 0x556cddca8b64 <unknown>\n#12 0x556cddc85f12 <unknown>\n#13 0x556cddca857f <unknown>\n#14 0x556cddc85cd3 <unknown>\n#15 0x556cddc52b8e <unknown>\n#16 0x556cddc537b1 <unknown>\n#17 0x556cde2424e0 <unknown>\n#18 0x556cde2457a5 <unknown>\n#19 0x556cde2451da <unknown>\n#20 0x556cde245c05 <unknown>\n#21 0x556cde231f29 <unknown>\n#22 0x556cde245f67 <unknown>\n#23 0x556cde21a426 <unknown>\n#24 0x556cde26c5f5 <unknown>\n#25 0x556cde26c7d3 <unknown>\n#26 0x556cde27e86a <unknown>\n#27 0x151ad28ad1f5 <unknown>\n
2026-06-27 20:51:44 DEBUG    ReqId 22780426540736 Response => POST /v1 body: {'status': 'error', 'message': 'Error: Error solving the challenge. Message: unknown error: net::ERR_CONNECTION_REFUSED\\n  (Session info: chrome=148.0.7778.178)\\nStacktrace:\\n#0 0x556cde27fcfe <unknown>\\n#1 0x556cddc0ff34 <unknown>\\n#2 0x556cddc0ced4 <unknown>\\n#3 0x556cddbf7c35 <unknown>\\n#4 0x556cddbf9833 <unknown>\\n#5 0x556cddbf7f82 <unknown>\\n#6 0x556cddbf77e1 <unknown>\\n#7 0x556cddbf7739 <unknown>\\n#8 0x556cddbf5b4a <unknown>\\n#9 0x556cddbf5e7a <unknown>\\n#10 0x556cddc13fea <unknown>\\n#11 0x556cddca8b64 <unknown>\\n#12 0x556cddc85f12 <unknown>\\n#13 0x556cddca857f <unknown>\\n#14 0x556cddc85cd3 <unknown>\\n#15 0x556cddc52b8e <unknown>\\n#16 0x556cddc537b1 <unknown>\\n#17 0x556cde2424e0 <unknown>\\n#18 0x556cde2457a5 <unknown>\\n#19 0x556cde2451da <unknown>\\n#20 0x556cde245c05 <unknown>\\n#21 0x556cde231f29 <unknown>\\n#22 0x556cde245f67 <unknown>\\n#23 0x556cde21a426 <unknown>\\n#24 0x556cde26c5f5 <unknown>\\n#25 0x556cde26c7d3 <unknown>\\n#26 0x556cde27e86a <unknown>\\n#27 0x151ad28ad1f5 <unknown>\\n', 'startTimestamp': 1782593500184, 'endTimestamp': 1782593504440, 'version': '3.5.0'}
2026-06-27 20:51:44 INFO     ReqId 22780426540736 Response in 4.256 s
2026-06-27 20:51:44 INFO     ReqId 22780426540736 172.19.0.3 POST http://flaresolverr:8191/v1 500 Internal Server Error

This is making me feel like my tachidesk install is not making a proper request to the filesolverr instance. I double checked the filesolverr url and it looks right with the value "http://flaresolverr:8191".

Please let me know if need anything else from me. Your assistance is greatly appreciated.

Okay,

we seem to have two problems. First we need to get flaresolver to talk to tachidesk, second magakakalot seems to be one of the most ip-ban friendly agregators out there.

For the first one:

open the console of tachidesk and type curl http://flaresolverr:8191

If we get a failed to connect message we need to recheck the network setup; send the docker run of both containers for that.

if we get the flaresolverr message body we check the tachidesk settings.

Go to tachidesk webui goto settings --> server --> scroll down, there should be a flaresolver section. Here my setup: grafik.png

Now for the second problem. Mangakakalot seems to have a low threshold for ip bans to keep bots away. See https://github.com/keiyoushi/extensions-source/issues/13106. Recheck in your webbrowser if you can reach the site. If you get a bad response your ip got banned. In that case offload some titles away from mangakakalot. First try changing kakalot mirror; see here (from previous link discussion): grafik.png

Further we should migrate some titels away. My extension recommendations would be in order of priority:

  • specific website of scanlator

  • Mangadex

  • MangaK (former batato)

  • other sites (if batoto doesn't have it, search the title in your search engine and check if the resulting aggregators have an extension and then select one of those.)

Kind Regards!

For the first one:

open the console of tachidesk and type curl http://flaresolverr:8191

If we get a failed to connect message we need to recheck the network setup; send the docker run of both containers for that.

When I run the command "curl http://flaresolverr:8191" from the Tachidesk console I get the following output:

$ curl http://flaresolverr:8191
{"msg": "FlareSolverr is ready!", "version": "3.5.0", "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36"}$ 

I believe this would indicate that the Tachidesk Container is able to connect to the Flaresolverr container without an issue and the network setup is working.

These are the settings in my tachidesk web ui:

image.png

Whenever I try to access the Mangakakalot extension, I get that 0.0.0.0:443 error and I don't see any activity in the flaresolverr container logs. When I run the following curl command "curl -X POST http://flaresolverr:8191/v1 -H "Content-Type: application/json" -d '{"cmd": "request.get", "url": "https://mangakakalot.gg", "maxTimeout": 60000}'" from the Tachidesk console, I see activity from the flaresolverr logs. So it looks like for some reason my tachidesk docker container is refusing to access flaresolverr even though it should be configured. I am running "ghcr.io/suwayomi/suwayomi-server:latest" for my Tachidesk-Server repository.

I will admit that this issue is frustrating because I have Suwayomi installed on my Windows desktop and want to migrate it to my Unraid server. On the Windows Suwayomi install, I have the same extension repositories and don't have flaresolverr configured. I have no issue connecting to Mangakakalot and other extension where I see the similar 0.0.0.0:443 and invalid SSL message errors.

I did try your suggested extensions and some others like:

  • Batcave - Works

  • MangaDex - Works

  • MangaFox - Works

  • MangaForFree.net - Does not work with :Unsupported or unrecognized SSL message"

  • MangaK -Works

  • MangaPanda.onl - Works

  • Mangasushi - Works

  • Read Comics Online - Works (accesses flaresolverr)

  • XOXO Comics - Works (accesses flaresolverr)

So based on the above test of some extensions, it likely indicates that the issue originates with the extension. If you feel that is about right then I think my instance is running properly.

  • Author
13 hours ago, bubdub said:

When I run the command "curl http://flaresolverr:8191" from the Tachidesk console I get the following output:

$ curl http://flaresolverr:8191
{"msg": "FlareSolverr is ready!", "version": "3.5.0", "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36"}$ 

I believe this would indicate that the Tachidesk Container is able to connect to the Flaresolverr container without an issue and the network setup is working.

These are the settings in my tachidesk web ui:

image.png

Whenever I try to access the Mangakakalot extension, I get that 0.0.0.0:443 error and I don't see any activity in the flaresolverr container logs. When I run the following curl command "curl -X POST http://flaresolverr:8191/v1 -H "Content-Type: application/json" -d '{"cmd": "request.get", "url": "https://mangakakalot.gg", "maxTimeout": 60000}'" from the Tachidesk console, I see activity from the flaresolverr logs. So it looks like for some reason my tachidesk docker container is refusing to access flaresolverr even though it should be configured. I am running "ghcr.io/suwayomi/suwayomi-server:latest" for my Tachidesk-Server repository.

I will admit that this issue is frustrating because I have Suwayomi installed on my Windows desktop and want to migrate it to my Unraid server. On the Windows Suwayomi install, I have the same extension repositories and don't have flaresolverr configured. I have no issue connecting to Mangakakalot and other extension where I see the similar 0.0.0.0:443 and invalid SSL message errors.

I did try your suggested extensions and some others like:

  • Batcave - Works

  • MangaDex - Works

  • MangaFox - Works

  • MangaForFree.net - Does not work with :Unsupported or unrecognized SSL message"

  • MangaK -Works

  • MangaPanda.onl - Works

  • Mangasushi - Works

  • Read Comics Online - Works (accesses flaresolverr)

  • XOXO Comics - Works (accesses flaresolverr)

So based on the above test of some extensions, it likely indicates that the issue originates with the extension. If you feel that is about right then I think my instance is running properly.

Ok,

Networks works. Tachidesk can access cloudflared too.

I think the reason Tachidesk doesn't access Flaresolverr is because it gets the some other http status code. Flaresolverr only get's accessed when Tachidesk needs it to solve a captcha.

It's good that it works on the windows pc (which client do you use there?), we can backtrack from there.

So what are the differences between the both setups?

Are the unraid host and Windows machine on the same network, and or the same internet connection? Is any of those using an vpn for internet access? Do your unraid server and windows machine use the same dns server and do they get the same answers?(Check with nslookup mangakakalot.gg on both machines; the container doesn't have the command, use the unraid console) If you still have the dns command on the container remove it.

In the github keiyoushi issues tab the reasons i've seen so far for managakakalot to not work are only Ip-ratebans for too many requests. But that would affect the windows setup too(if they are on the same network). Otherwise you can try the different mangakakalot mirrors in the extension settings. Otherwise an old Tachiyomi post suggested deactivating dns over https, but suwayomi doesn't have that, so your upstream dns server decides that.

Lastly enable debug logs in tachidesk and check what it says. Heres mine:

grafik.png

One should first get the 403, then it should recheck over flaresolverr to get workable cookies and smoot sailing from there.

Maybe one of the closed issues could help too: https://github.com/keiyoushi/extensions-source/issues?q=is%3Aissue%20state%3Aclosed%20mangakakalot

Kind Regards

Edited by C3004
typo

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.