ungoogled-software / ungoogled-chromium

Google Chromium, sans integration with Google
BSD 3-Clause "New" or "Revised" License
20.79k stars 843 forks source link

Not able to put in a custom DOH address #2093

Closed haptizum closed 3 months ago

haptizum commented 2 years ago

OS/Platform

Arch Linux

Installed

OS/Platform's package manager

Version

105.0.5195.125

Have you tested that this is not an upstream issue or an issue with your configuration?

Description

Issue Adding A Custom DOH Service Provider

How to Reproduce?

Naviagte to: Privacy and Security => Security Advanced => Use secure DNS => With Custom

Copy or manually add a custom DOH service provider

Actual behaviour

Tried to add Quad9 to Chromium and I am getting an error.

When I use https://dns.quad9.net/dns-query I get the error message, "Please verify that this is a valid provider or try again later".

This is also happens with other DOH service providers like BlahDNS and UncensoredDNS.

Expected behaviour

After adding a DOH servcie provider I should be able to hit enter for Chromium to accept it.

Relevant log output

No response

Additional context

No response

networkException commented 2 years ago

I'm pretty sure this is just an UI problem, from what I can tell it makes requests to the DOH server just fine

PF4Public commented 1 year ago

Is this still an issue?

networkException commented 1 year ago

Yes it uses the DOH server just fine but still complains in UI

John4266 commented 1 year ago

Happens to me too. Getting this error but the DNS still works. image Version 110.0.5481.100 (Official Build, ungoogled-chromium) (64-bit)

pferreir commented 1 year ago

Same here.

m0x61h0x64i commented 11 months ago

I have same issue, any updates?

stnert commented 9 months ago

And until when will we continue without a correction?

networkException commented 9 months ago

Until someone is willing to implement a fix (again, to my knowledge this is purely visual).

JohnnyMysterious commented 7 months ago

As of 12/04/2024 the UI error still exists but it has successfully been connected to my private dns server and I can see the logs. So it's not a big issue but still would be good if it gets fixed.

t0ma5 commented 4 months ago

As of 19/07/2024 the UI error still exists