app permanently and irrevocably broken when some VPNs are in use

[Aleximal]

Preliminary checklist

• I have read the README.
• I have searched the existing issues for my problem. This is a new ticket, NOT a duplicate or related to another open issue.
• I have read the FAQs.
• I have updated Cromite to the latest version. The bug is reproducible on this latest version.
• This is a bug report about the Cromite browser; not the website nor F-Droid nor anything else.

Can the bug be reproduced with corresponding Chromium version?

No

Are you sure?

Yes

Cromite version

145.0.7632.120

Device architecture

arm

Platform version

Android 15

Android Device model

Google Pixel 6 and actually it is Android 16

Is the device rooted?

No

Changed flags

no flags changes

Is this bug happening ONLY in an incognito tab?

No

Is this bug caused by the adblocker?

No

Is this bug a crash?

no

Describe the bug

any site goes to "suddenly closed connection" when VPN in use

Steps to reproduce the bug

Have VPN (i use Karing app)

Activate VPN

Try to navigate to website

Expected behavior

site open

Screenshots

instead site does not load, says "suddenly closed connection"

[opzch]

Steps to reproduce the bug
Have VPN (i use Karing app)

This is not a VPN, but all apps of this type rely on redirecting DNS requests. Check that it doesn't use secure DNS:
Settings -> Privacy and security -> Use secure DNS -> Off
Also make sure that Private DNS is disabled in Android network settings. Also check the app (Karing) for DNS-related settings (for example, in nekobox it's called FakeDNS, should be enabled).

[Aleximal]

Steps to reproduce the bug
Have VPN (i use Karing app)

This is not a VPN, but all apps of this type rely on redirecting DNS requests. Check that this is does not use secure DNS: Settings -> Privacy and security -> Use secure DNS -> Off Also make sure that Private DNS is disabled in Android network settings. Also check the app (Karing) for DNS-related settings (for example, in nekobox it's called FakeDNS, should be enabled).

amazing

Disabling secure DNS in the settings (of Cromite) worked but even better, enabling it (in Cromite) and then
switching Karing to using TLS only DNS servers inside the tunnel (I'm wary of FakeIP option) has apparently fixed the mystery issue

Not sure whether it is an "issue closed" or a workaround.

Is it normal that Cromite responds to "full" HTTPS DNS servers "like that" ? gently tagging @uazo because now I am super curious

such a weird interaction

[Aleximal]

okay, I was wrong
the issue is back and the "set all DNSes to TLS" in the Karing, and/or disable secure DNS in Cromite does not help anymore

It seems to "wax and wane"

Other browsers work.

@opzch any more ideas ?

[Aleximal]

changing all in-tunnel DNS to TLS and then resolution method to fake IP seems to have "fixed" it

[uazo]

I really don’t know what ‘Karin’ is, but if you’ve sorted it out, I can’t see how it could be a browser issue.

Disabling secure DNS in the settings (of Cromite) worked but even better

If you disable that flag, Cromite uses the Android APIs to resolve the DNS.

Is it normal that Cromite responds to "full" HTTPS DNS servers "like that" ?

Sorry, I don't understand.

[github-actions]

This issue has been automatically marked as stale as there has been no recent activity in response to our request for more information. Please respond so that we can proceed with this issue.

[github-actions]

This issue has been automatically closed as sufficient information hasn't been provided on the issue for further actions to be taken. Feel free to add more information.