Could not connect to SABnzbd

[shomilsaini]

Saw the updated extension today.
Firstly, the settings were messed up after upgrade. Secondly, it always shows this error even when connection test is successful (pictures below) - Could not connect to SABnzbd - Check it is running, the details in this plugin's settings are correct and that you are running at least SABnzbd version 0.5!

Thanks for the hard work and continued support of this extension. My previous extension was also working fine though I dont know how to downgrade to previous version now.

[bertrandom]

Seeing the same!

[bertrandom]

Actually, I cloned the repo and loaded the unpacked extension in Chrome. After reloading the extension once, it started working again? So I suspect some sort of incompatibility with what was in the store from the previous extension?

[thiagohartmann]

Having the same issue.

[shomilsaini]

Also, on a side note. I didn't need the new extension yet. Because I have enabled MV2 support in chrome so the old one would have worked fine. But this was auto upgraded by chrome as I understand.

I'm moving to librewolf in the background and once that's done, I'll check this again on my new browser. Screw google chrome!

Thanks!

[BillBlight]

Same Issue here .. :(

[TheseUserNamesAreMakingMeThirsty]

Go into settings and update/change the refresh rate. Mine had that error while connected but it went after I enabled refresh rate.

[v1rusnl]

Go into settings and update/change the refresh rate. Mine had that error while connected but it went after I enabled refresh rate.

Doesn't do anything in my Browser.

@bertrandom 's suggestion did work though. Wiped the store version from my Brwoser, installed local Repo download, work instantly.

[ampersandru]

was working, then stopped working again today. Latest Sab is 4.5.5, why is it requiring 0.5?

[treyturner]

was working, then stopped working again today. Latest Sab is 4.5.5, why is it requiring 0.5?

That's a generic error message for "couldn't hit the API". Not sure if this is the cause of the OP, but I'm here because within the past couple of days my installation has started throwing this error. It seems to be produced by CORS policies being applied either by SABnzbd or maybe Chromium as a new default (I'm in Brave).

Access to fetch at 'http://mydomain.tld:8800/api?apikey=redacted&ma_username=redacted&output=json&mode=queue&limit=5' from origin 'chrome-extension://okphadhbbjadcifjplhifajfacbkkbod' has been blocked by CORS policy: Permission was denied for this request to access the `unknown` address space.

[MangoTwo2]

Hey guys. This is a regression in Chrom(ium) itself. Until google fixes it, you can make it work by disabling chrome://flags -> Local Network Access Checks

[Hitcher]

@MangoTwo2 thanks for the heads up.

[shomilsaini]

Hey guys. This is a regression in Chrom(ium) itself. Until google fixes it, you can make it work by disabling chrome://flags -> Local Network Access Checks

Thanks for the response @MangoTwo2. This works for now.

[shomilsaini]

@MangoTwo2 , @gboudreau - Any updates on this?
Thanks

[AdminVin]

@MangoTwo2 , @gboudreau - Any updates on this? Thanks

Purge your existing install, restart Chrome, and then configure to your SAB. Working flawlessly now.