AdguardTeam / AdguardTeam/CoreLibs

Browser uses the default certificate after re-enabling protection

Open
#1,832 4 comments 0 reactions 1 assignee Claimed by @sfionov View on GitHub
Bug Priority: P4
Dominant language
No language data
Stars
52
Forks
10
PR merge metrics
No merged PRs in 30d

Description

### Please answer the following questions for yourself before submitting an issue.

- [X] I am running the latest version
- [X] I checked the documentation and found no answer
- [X] I checked to make sure that this issue has not already been filed

### AdGuard version

4.3n21

### Environment

```markdown
- OS: Android 11
- Device: POCO F1
```

### Root access

- [X] Yes, I have it.

### What filters do you have enabled?

AdGuard Base filter, AdGuard Mobile Ads filter, AdGuard Russian filter, AdGuard Tracking Protection filter, AdGuard URL Tracking filter, AdGuard Social Media filter, AdGuard Annoyances filter

### What Stealth Mode options do you have enabled?

_No response_

### Issue Details

Steps to reproduce:
1. Disable protection
2. Open `github.com` in Chrome
3. Check the certificate and you will see it's given by `DigiCert`
4. Return to app and enable protection
5. Refresh the page.

### Expected Behavior

The certificate must be provided by AdGuard.

### Actual Behavior

The certificate are provided by DigiCert.

### Screenshots

Screenshot 1:

### Additional Information

_No response_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.