automatic proxy not working on chromium derived browsers

[catbabylon]

Please answer the following questions for yourself before submitting an issue

• Filters were updated before reproducing an issue
• I checked the knowledge base and found no answer
• I checked to make sure that this issue has not already been filed

AdGuard CLI version

1.2.13

Browser version

up to date versions of vivaldi, edge, ulaa

OS version

CachyOS

Issue Details

Steps to reproduce:

1. add brower entries to browsers.yaml if required i.e. vivaldi-stable, ulaa-browser-stable, microsoft-edge-stable
2. start adguard-cli in automatic proxy mode
3. check on firefox or chromium that they work with https filtering by looking at a website and seeing if the certificate is the original or adguard's
4. see chrome://certificate-manager on browsers to see that the certificate is indeed imported from linux
5. load a web page on one of the affected browsers, where the certificate shows that it is the original website and not adguard's

Expected Behavior

having checked browser.yaml vivaldi is included, so would expect it to work out of the box. testing also with other chromium based browsers installed natively on cachyos and adding them to browsers.yaml and would expect them to work with the auto proxy mode

Actual Behavior

firefox and chromium work fine but vivaldi edge and ulaa all don't seem to be using https filtering (going by the fact that they aren't using adguard's certificate on any web page. at first I thought it was that browser.yaml has 'vivaldi' rather than 'vivaldi-stable' but that didn't make any difference. as above, adding the other browsers to see if it was a problem unique to vivaldi showed that it seems to happen on many chromium based browsers but I can't figure out why. Manual proxy works OK

Screenshots

Screenshot 1

Additional Information

No response

[catbabylon]

sod's law that I find out the cause of the issue seconds after I submit the bug. The entries on browser.yaml needs to exactly the same as the process name of the browser. So they need to be: vivaldi-bin, ms-edge, and ulaa (or whatever your system monitor says they are called as it might be different on different distros)

[murattkr]

I'm having the same problem with the Yandex browser, and I haven't been able to find a solution.

[balupton]

So they need to be: vivaldi-bin

fixed it for me, thanks!