Is IPCTDDNS still working for everyone who uses cloudflare DNS?

[LBJ]

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' "

https://ipcamtalk.com/dyn?api=1234567890

"

homepage: 403
dyn: 403

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. .

 

[jeremyx]

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.

 

[bp2008]

@Mike and/or @bigballerbill would need to fix this!

 

[Mark_M]

Since Sept 24, requests to ipcamtalk.com from non-browser clients return HTTP 403 with a Cloudflare managed-challenge page.

I've found this to be an issue since November 2025.

IPCT Post in thread 'Introducing IPCT DDNS! Free DDNS service!'

Nov 29, 2025

Is IPCT DDNS behind Cloudflare bot protection?
My router is consistently failing at updating it.

stdout: >-
  <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><meta
  http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta
  http-equiv="X-UA-Compatible" content="IE=Edge"><meta name="robots"
  content="noindex,nofollow"><meta name="viewport"...

• Mark_M

I did manage to make it work via Home Assistant though:

shell_command: 
  update_ipct_ddns: >
    curl -H "User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" \
     -H "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" \
     -H "Accept-Language: en-US,en;q=0.9" \
     -H "Accept-Encoding: gzip, deflate, br" \
     -H "DNT: 1" \
     -H "Connection: keep-alive" \
     -H "Upgrade-Insecure-Requests: 1" \
     -H "Sec-Fetch-Dest: document" \
     -H "Sec-Fetch-Mode: navigate" \
     -H "Sec-Fetch-Site: none" \
     -H "Sec-Fetch-User: ?1" \
     "https://ipcamtalk.com/dyn?api=xxxxxxxxx"

 

[LBJ]

I got it working again on my Raspberry Pi DDNS updater using the Home Assistant code from Mark_M as a baseline. That was a very useful post.

thanks