Is IPCTDDNS still working for everyone who uses cloudflare DNS?

LBJ

LBJ

n3wb
Jul 9, 2016
28
15
Since Sept 24, requests to ipcamtalk.com from non-browser clients return HTTP 403 with a Cloudflare managed-challenge page.

curl -4 -sS -o /dev/null -w 'homepage: %{http_code}\n' Home
curl -4 -sS -o /dev/null -w 'dyn: %{http_code}\n' ""
Click to expand...
homepage: 403
dyn: 403
Click to expand...

This affects the homepage as well as /dyn, so it isn't specific to the DDNS path. It loads fine in a browser.

Since Blue Iris Tools, the Asus integration, and curl all make plain HTTP requests, DDNS updates might have issues for those using Cloudflare as a DNS.

so I thought I'd check to see if others had a similar issue. .
 
Seeing the same from a non-browser client just now: both the homepage and /dyn return HTTP 403 with the Cloudflare managed-challenge page, while a normal browser session loads fine.

So it is not limited to DDNS or to one API key. Plain clients (curl, Blue Iris Tools, Asus DDNS) cannot complete that challenge, so IPCTDDNS updates over /dyn will keep failing until the challenge is skipped for that path (or for non-browser clients) on the Cloudflare side.

Until that is adjusted, the practical workaround is to point the hostname update at another DDNS provider temporarily. Browser access to the forum itself is unaffected.
 
You must log in or register to reply here.
Top Bottom