API is not started by browser in chrome, in fedora

[robincajas12]

It run the python script and, no errors pop up, then go to yomitan and try to connect the message is
Failed to fetch. Try again in a moment. The nativemessaging component can take a few seconds to start.
my pc is fedora

error.log does not show anything also

[MayADevBe]

I have the same issue, also Fedora + Chrome browser.
I followed the installation guide and no error. I got the following error in the console, that I believe could the issue (?):

log.js:138 Yomitan Popup Dictionary 26.4.6.0 has encountered a problem.
Originating URL: chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/sw.js
Error: Specified native messaging host not found.
    at YomitanApi._onDisconnect (chrome-extension://likgccmbimhjbgkjambclfkhldnlhbnn/js/comm/yomitan-api.js:564:23)

Issues can be reported at https://github.com/yomidevs/yomitan/issues

I am however not familiar enough with Native Massaging to be sure.

Note: When attempting to manually start the python script I can run a test and it will say 'connection was successful', but it still doesn't work (when trying to use asbplayer)...
Here is the output of the script in case it could help:

$ python yomitan_api.py 
127.0.0.1 - - [27/Apr/2026 19:51:57] "POST /serverVersion HTTP/1.1" 200 -
127.0.0.1 - - [27/Apr/2026 19:56:11] "POST /serverVersion HTTP/1.1" 200 -
8{"action": "yomitanVersion", "params": {}, "body": "{}"}

[Kayanchi]

I also installed the yomitan api without any errors and it also doesn't seem to start on its own.

Manually starting the .bat allows me to get the Connection was successful message when testing the API in yomitan.
however opening the asbplayer annotation settings (where it tries to connect to the yomitan api) causes this message
8{"action": "yomitanVersion", "params": {}, "body": "{}"}
after which testing the API in yomitan fails and no new console messages appear (crash?)

Also I noticed that, in both Brave and Chrome, this error appears in the extension's console (service worker) whenever Enable API is clicked (before even hitting Test).
Not sure if that's the exact cause, but it surely doesn't help

[Kuuuube]

Manually starting the .bat allows me to get the Connection was successful message when testing the API in yomitan

Yomitan tests the API by making an API call to it for the API component's version. It doesn't request a path that interacts with Yomitan to test the round trip. Maybe it should. It will never work properly if you just run it manually. The browser has to have it as a child process.

this error appears in the extension's console

When you enable the API, Yomitan tries to start the API. That error is the browser saying it doesn't even know what a native messaging component is. It's not even a "failed to start" error. It's saying it's not even possible to start a native messaging component in the first place.

Maybe this is a permissions error. Yomitan should be checking permissions when you enable the API. But maybe the browser is misreporting. Go to the Yomitan permissions page (button at the bottom of settings) and make sure nativeMessaging is enabled. Maybe turn it off and on if it already is.

[Kayanchi]

I'm now getting this error when trying to turn it on