While it prevents you from using another VPN at the same time, that’s not the biggest deal for me since the only reason I run a real VPN is to watch regional media.Īnother issue you have to get around is AdGuard’s shoddy implementation of a local VPN on ChromeOS. This problem can be mitigated by running a Proxy manager, which our forthcoming CrosManager extension can help out with!īut even if you do that, you can only run this in the Android environment, and even there you won’t be able to access all of AdGuard’s features. Local Proxy blocking doesn’t work in ChromeOS (image by author)Īnother problem with the Proxy method is that it requires fiddling with the ChromeOS network settings to turn on/off. To do that, search for “certificates” in the browser settings, and import the downloaded adguard.crt in the “Authorities” tab. The AdGuard certificate is successfully installed and HTTPS filtering works now!Įven if the HTTP certificate installs automatically for Android, you’ll always have to export it to install it on ChromeOS. A CA certificate installed toast message should show up Select the recently downloaded AdGuard certificate. Read through it and tap Install anyway to proceed Tap on Install certificate and then on CA certificateĪ warning message will appear. Scroll down to Advanced, open it and then tap on Encryption & credentials (these settings may be called variously on different devices - the main thing is to choose advanced security settings) Tap on the Open security settings button there Go to the app’s main screen and tap Turn on next to the HTTPS filtering is off message (it will be highlighted in orange if AdGuard certificate is not installed yet)Ī new screen will appear, tap on the Next button, then again on the Next and then on Save it now when prompted to download an AdGuard certificateĪfter the certificate is downloaded, you will see a new screen. I think this is more about Android 9 vs 11, and how ChromeOS is just not optimized for the latter despite Android 13 being on the horizon.Īnyway, if you’re running into this issue, you need to do a manual install, as outlined on AdGuard’s website. But on my x86 Chromebooks, the onboarding process couldn’t complete. On my ARM tablets (HP X2, Lenovo Duet), it installed without issue. Here’s where we run into our first problem - Some devices will not accept the HTTP certificate install method.
0 kommentar(er)
