...

[ghost]

...

[IkelAtomig]

Maybe you need to update Instances ?

[2084x]

Same issue here. Being redirect to instances I haven't selected. Being redirected to libreddit when I have teddit selected etc. I've tried updating instances and doing all my settings again. Gonna try a reinstall now I guess.

Arch linux - Brave - libredirect 2.3.1

[2084x]

Reinstalling changed nothing, but exporting settings --> manually edit json file --> import settings got everything to save and work for now.

[Impeta]

Reinstalling changed nothing, but exporting settings --> manually edit json file --> import settings got everything to save and work for now.

That did it! That's got to be a dumb workaround, but worked for me, lol.
Celebrated too soon. Actually, it only works if you edit a chosen section of instance list to redirect for a social media, in order to make it work through. This means for the time being, you have to edit up each section manually first, and then (only they, others will be wiped off without warrant still) they will work after you import it in.
I'm on EndeavourOS, Firefox 105.0.3, libredirect 2.3.1.

[JacobKfromIRC]

On version 2.3.4 this seems to still be happening. It does not seem to happen on a clean install, but an old install updated to 2.3.4 is still having the problem. I'm getting sent to domains such as searx.loafland.xyz when searching and invidious.osi.kr when YouTubing. Exporting and importing to a different Abrowser/Firefox profile also seems to fix the problem.

I suspect the problem remains on the old install because however instances are removed only removes them from the "redirects" key, whereas when actually redirecting the extension is looking at the protocol-specific key (e.g. "searxngNormalRedirectsChecks"), which doesn't exist in new installs but takes precendence over the new value.

Should I open a new issue for this?

[IkelAtomig]

No. I think better export your settings. Reset and import. That would be the only for this ?
Kai, What do you think ?

[JacobKfromIRC]

Would it be reasonable to detect this issue and then automatically silently export and re-import to fix it? That way people who don't know about or how to deal with this issue don't have to spend time troubleshooting. These are hypothetical people, so maybe it's not really that important.

[IkelAtomig]

There isn't anyway to detect and silently do this. If we do, It would increase codebase by a large scale and tedious.

We better mention in FAQ about trying resetting.

[JacobKfromIRC]

Okay, I think that is reasonable.

Is there a good way to make a backup in a way that preserves the issue? I tried copying the extension folders in storage/default but they seem to have a different name for each profile, and renaming them to fit a different profile doesn't seem to work for some reason. I guess copying the entire profile root folder should be sufficient, but I'm not sure how to check that.