Checked whatsmydns and tried to get the discord app site to let me save the correct address to the same results. Red X’s across the board. I deleted and remade the dns record, and verified, every way possible, that the records and setting on my system are all fine.
I followed all the logical troubleshooting steps:
Verified the Cloudflare Tunnel (cloudflared) service is running with the correct Tunnel ID (c4a6…).
Confirmed the Cloudflare DNS CNAME record points exactly to the correct tunnel target and is Proxied.
Confirmed the parent domain resolves to Cloudflare nameservers correctly.
Confirmed DNSSEC is disabled.
Confirmed basic Cloudflare security features (Bot Fight Mode, Firewall Events, Security Level) are not blocking requests.
Deleted and recreated the problematic CNAME record.
What feature, service or problem is this related to?
I can access it all just fine but the dns doesn’t seem to work properly. If you check it via https://www.whatsmydns.net/ you can see that it has issues and discords bot app gives
Validation errors:
interactions_endpoint_url: The specified interactions endpoint url could not be verified.
I tried changing it to A from CNAME and here are the results:
A Record Propagates: The whatsmydns screenshot showing mostly green checkmarks for the A record proves that standard A records are propagating correctly for my trevor333 zone through Cloudflare’s DNS. The IP addresses shown (104.21…, 172.67…) are Cloudflare’s edge IPs, which is expected because the record is proxied.
CNAME Record Failed to Propagate: Comparing this to the previous whatsmydns result (all red X’s) for the CNAME record confirms that there was/is a specific problem preventing the CNAME record (pointing to the tunnel) from resolving globally.
Discord Still Fails: Discord verification fails with the A record because, as anticipated, Cloudflare doesn’t know how to route the request to your specific tunnel without the CNAME pointing to <YOUR_TUNNEL_ID> dot cfargotunnel dot com. The A record tells Cloudflare that the hostname exists and is proxied, but it lacks the crucial information linking it to your active cloudflared service via the tunnel ID. The request hits Cloudflare’s edge but doesn’t get forwarded down the tunnel to n8n.
I would also like to add that the block on new users using more than 4 links on a post is SO frustrating and unnecessary! Especially when the forum makes links from anything that is related to cloudflare.
Sorry I’m unsure what issue you’re having. You have a record which resolves in DNS to a Cloudflare tunnel. That record has to be proxied because it points to a Cloudflare tunnel. A record which is proxies will always fail to return a CNAME result because Cloudflare is proxying it. If you need a record which is a CNAME to return a specific value it should be set to DNS only.
What’s the discord problem? As George’s screenshot indicates n8n.trevor333.uk hitting whatever n8n is. So The request hits Cloudflare’s edge but doesn’t get forwarded down the tunnel to n8n. doesn’t appear to be true.
How have you determined that this is a DNS issue? Have you reviewed your security logs to make sure this request isn’t being blocked by a WAF or other security rule? Have you reviewed the application logs on the server runing the software to confirm the request isn’t being received?
I’m not sure who has provided this feedback, but it’s likely not correct. For the moment I would assume the tunnel works just fine since there is a login page displayed when visiting the site.
I am just trying to eliminate all possibilities starting with this. It could be one of many issues and I want to make sure I have done everything possible to check that it is not a DNS issue first is all.
Since the link thing is going on it is hard to tell you everything that is going on so I created a pastebin to explain everything. At this point I have exhausted my limited knowledge and everything that Gemini has to offer for suggestions.
The person who wrote this is incorrect DNS is working fine as evidenced by the fact the site loads when you access it in a browser. The CNAME doesn’t resolve as a CNAME when Cloudflare proxy is active because that how Cloudflare works. It resolves as an A record.
That is not a problem it is expected behavior.
https://n8n.trevor333.uk/webhook/dnd-bot returns the following to a get request. I have no idea what a post request is supposed to look like but the problem isn’t DNS.
{“code”:404,“message”:“This webhook is not registered for GET requests. Did you mean to make a POST request?”}
Have you reviewed the WAF events yet? Has whoever is helping you sent a post request to the web server? What is the response to that request?
I am on a free account so I am limited on what I can do/ see as far as WAF. As for who is helping me I have no one, just using the AI Gemini 2.5 and what little knowledge I have to try and figure this out.
Since DNS is fine and GET requests are reaching the n8n webhook node, the failure of Discord’s POST request verification must be happening for one of these reasons:
Cloudflare Blocking the POST: Even though basic Firewall Events are clear, Cloudflare might be blocking the specific POST request from Discord for other reasons not logged there (e.g., WAF Managed Rules if any are active, Rate Limiting, or other security features). The forum member asking “Have you reviewed the WAF events yet?” is pointing back to this.
cloudflared Error Handling POST: Less likely now, but the tunnel service might have issues specifically proxying POST requests or their responses.
n8n Failing to Send PONG: Despite the green checkmark, there could be a subtle error in how n8n sends the {“type”:1} response back specifically for the PING request.
Discord Expectation Mismatch: Discord might expect specific headers or timing for the PONG response that isn’t being met.
At this point I am just copying and pasting what Gemini says in response.
