#ASB Player won't connect to Anki no matter what

15 messages · Page 1 of 1 (latest)

haughty ledge
#

I have tried changing the config in the anki connect add on, i've even tried deleting and re-installing the addon as well as deleting and re-installing ASB. What's weird though is that on the quick menu in ASB everything looks connected and there is no error message but on the main settings page I always get the "Failed to fetch" message.

exotic sable
#

Hey @haughty ledge , have you already had a glance at this point on the ASB player faq? - https://docs.asbplayer.dev/docs/common-issues#asbplayer-cant-connect-to-anki-it-shows-an-error-message-eg-failed-to-fetch

If it isn't one of those common causes mentioned there, maybe you could find more information through your browser's devtools. The debug console and any available network inspection tools would be good places to start. Are you able to provide any more info on your OS and browser? Are you using the latest versions of everything?

haughty ledge
#

on mac os version 26.2, anki version 25.09.2, asbplayer version 1.13, lasteest version for all of those things. Also on the
version of google chrome

#

tried turning offf the web features but that also did not work

#

This seems to be the only issue in the console whihc isn't related to asb

#

ahh

#

i get this when opening asb

#

how do i activate though

#

still nothing working here

exotic sable
#

@haughty ledge I would have expected that you'd see some kind of pop-up window about giving the site permissions to access local network addresses at some point. If you didn't, it might be worth checking in the site-settings menu for the ASB player site: https://support.google.com/chrome/answer/114662
Once you've found it, look for the local network access perm and set it to allow if it isn't already. The console error might be unrelated tbh, I see it too and I don't have connection issues.

You might be able to get more info if you click over to the network tab in the devtools and test the Anki connect URL again. If it's failing, there should be a red request addressed to 127.0.0.1. If you click that, you should be able to see more details there about the failed connection attempt that could be relevant. It might also be worth doing a simple smoke/sanity test of Anki connect if you haven't already. When you navigate to http://127.0.0.1:8765 in your browser, do you see some json formatted data about your AnkiConnect version?

haughty ledge
#

The local network perm was off whihc is odd because i've never messed with it

exotic sable
#

Ah, it was the permissions issue?

#

Nice, glad you were able to figure it out!

haughty ledge