Set my proxy status to "Proxied": dns_probe_finished_nxdomain

This error “dns_probe_finished_nxdomain” only occur in mobile user-agent, and works fine on desktop.

1 Like

I couldn’t reproduce that error. Probably you are seeing the cached version. Would you try clearing the browser cache or try using incognito mode?

I have set it back to the state I described, it should show up as error now. loads fine for me.

Edit: the above was with Firefox desktop. Using Firefox mobile, redirects to which returns an error.

1 Like

@bowen I affirm it. Check the redirect rule you’ve set.

1 Like

Can replicate with cURL by using a Android Useragent (note the location)

$ curl -I -A "Mozilla/5.0 (Android 13; Mobile; rv:109.0) Gecko/115.0 Firefox/115.0"
HTTP/2 302
date: Thu, 22 Jun 2023 06:23:09 GMT
cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
expires: Thu, 01 Jan 1970 00:00:01 GMT
report-to: {"endpoints":[{"url":"https:\/\/\/report\/v3?s=UBPniyk0djtPfNSAYDHyK2EG%2BXQzEnYZMZQ0b9OVVRsP%2FOnhvm3fuUF7czF9BjOgOi2b0dE8s7VgNPCfyAxhP2wx2zLNPPPjWL52GDKuQsIog4khOIdj1tf4ifVyUFWqEXBZg%2B%2F79A6PQ3%2B7PzfKQzinZQ%3D%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 7db266a4cd0b1f68-MEL
alt-svc: h3=":443"; ma=86400
1 Like

hey all appreciate the help! Is there anyway we can check where the redirect is coming from? I have tired deactivated all wordpress plugins and it doesn’t work. My cloudflare doesn’t have any page rules either.

It appears it is coming from Cloudflare somewhere. Connecting directly to the origin server IP (either) doesn’t return a location header

$ curl -I --resolve '' -A "Mozilla/5.0 (Android 13; Mobile; rv:109.0) Gecko/115.0 Firefox/115.0"
HTTP/2 200
date: Thu, 22 Jun 2023 07:31:01 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
vary: Accept-Encoding
vary: Accept-Encoding,Origin
wpx: 1
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"
x-turbo-charged-by: LiteSpeed
x-edge-location: WPX CLOUD/MEL01
cache-control: public,max-age=3600,stale-while-revalidate=21600
server: WPX CLOUD/MEL01
x-cache-status: HIT

while connection normally (or by replacing the IP in the command above with a Cloudflare IP) does return the location header (as previously shown) which causes the redirect.

What about other rules?


Page Rules - blank
Configuration Rules - blank
Transform Rules - blank
Redirect Rules - blank
Origin Rules - blank


Has anything to do with this:

If there’s nothing set here, check at your host.

Can you post a screenshot that shows your DNS records and the assigned Cloudflare nameservers that are right below it?

The following commands return results that are not consistent with what you have shown in your first screenshot. This suggests to me that the screenshot is not from the Cloudflare account in which the domain is active.

dig +short
dig +short

Hey i have attached the DNS pointing on the domain registrar end. I don’t see anything beside pointing to CF.


In your very first post, you have shown a screenshot that shows your DNS records in Cloudflare. If you go to the same menu and scroll down a little, you see a section Cloudflare Nameservers.

Can you post a screenshot of that section? Preferably one that is readable, because there is no way I can read the content of the screenshot you posted just now. Copy/Paste would also work.

1 Like

Here is the screenshot with the cloudflare namesevers.

I’ve also attached the screenshot from my domain registrar showing it pointing to CF

Unrelated to any issues you are having with anything else, you need to set to :grey: DNS Only. You can see from DNS queries that Cloudflare tries to compensate for this by publishing a synthetic record that begins with _dc-mx. The same goes for the ftp hostname if you expect to use it with FTP, SSH, or any protocols other thsn HTTP.

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.