pfSense

Tested on the:

2.6.0-RELEASE (amd64)
built on Mon Jan 31 19:57:53 UTC 2022
FreeBSD 12.3-STABLE

I replicated the issue. After finishing the DynDNS setup using CloudFlare service and clicking the Save or Save & Force Update it will not bring you back to the /services_dyndns.php page. After some time you will get 504 Gateway Time-out. But in my case, the settings were applied and the IP address got updated correctly.

After simulating the public IP address change the service pushed the new address to Cloudflare without any issues.

Here are related logs:

Feb 25 10:28:08     php-fpm     2514     /services_dyndns_edit.php: Response Header: server: cloudflare
Feb 25 10:28:08     php-fpm     2514     /services_dyndns_edit.php: Response Header:
Feb 25 10:28:08     php-fpm     2514     /services_dyndns_edit.php: Response Header:
Feb 25 10:28:08     php-fpm     2514     /services_dyndns_edit.php: Response Data: {"result":{"id":"xxxxx","zone_id":"xxxx","zone_name":"xxxx","name":"xxxx","type":"A","content":"109.x.x.x","proxiable":true,"proxied":false,"ttl":120,"locked":false,"meta":{"auto_added":false,"managed_by_apps":false,"managed_by_argo_tunnel":false},"created_on":"2022-02-25T09:27:35.439256Z","modified_on":"2022-02-25T10:13:24.990709Z"},"success":true,"errors":[],"messages":[]}
Feb 25 10:28:08     php-fpm     2514     /services_dyndns_edit.php: Dynamic DNS cloudflare (xx.xx.xx): _checkStatus() starting.
Feb 25 10:28:09     php-fpm     2514     /services_dyndns_edit.php: Dynamic DNS cloudflare (xx.xx.xx): 109.x.x.x extracted from Check IP Service
Feb 25 10:28:09     php-fpm     2514     /services_dyndns_edit.php: phpDynDNS: updating cache file /conf/dyndns_wancloudflare'xx.xx.xx'0.cache: 109.x.x.x
Feb 25 10:28:09     php-fpm     2514     /services_dyndns_edit.php: phpDynDNS (gate): (Success) gate updated to 109.x.x.x
Feb 25 10:31:05     nginx         2022/02/25 10:31:05 [error] 39537#100466: *1265 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 192.x.x.x, server: , request: "POST /services_dyndns_edit.php?id=0 HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "xx.x.xx", referrer: "https://xx.xx.oxx/services_dyndns_edit.php?id=0" 

But when you disconnect the converter or renew the public IP, the IP was not updated to clodflare. It just only update after the OS reboot. Just one time you save & force update, IP will be updated but take the 504 Gateway time-out on the pfsense. if you save and force many time like that, the pfsense will be crash, then you cannot access to the web control.
With google domain, the service completely not update the IP address. I take the issue after upgrade pfsense to version 2.6.0

Hong Duong Pham wrote in #note-5:

But when you disconnect the converter or renew the public IP, the IP was not updated to clodflare. It just only update after the OS reboot. Just one time you save & force update, IP will be updated but take the 504 Gateway time-out on the pfsense. if you save and force many time like that, the pfsense will be crash, then you cannot access to the web control.
With google domain, the service completely not update the IP address. I take the issue after upgrade pfsense to version 2.6.0

Hello,

Please provide logging data to show this is a bug. Otherwise, this is likely a configuration issue on your firewall, which would be a support issue as previously mentioned.

Please provide supporting documentation.

Logs is the same reply from Danilo Zrẹnanin. Please check !

Jim Pingle wrote in #note-14:

I can't reproduce this on any of my Namecheap entries on today's snapshot with the fix in place. Looks good to me.

This is great @jim. Are there any plans for a v26.1 dot release, or is this only going to make it to v27?

No plans for a point release at this time.

You can install the System Patches package and then create an entry for bdffb77d1aa21770b23ef408ad9fba79d0825ec5 to fetch and apply the fix. I may add that into the recommended patches list for 2.6.0/22.01 as well.

I was able to replicate this issue with GoDaddy DNS. Click Save & Force Update then eventually a 504/timeout error appears and the logs show the update was made successfully. I testing using pfSense 2.7.0.a.20221123.0600 and I the patch does not appear to be listed in the System Patches Recommended Patch list for 2.7.

Will this appear fix become part of 2.7 in an upcoming Devl build and/or the full release?

I think I have this fixed again, it's still weirdness in cURL.

With PHP 8, curl_close() does nothing, which explains why it worked for a while and then broke -- curl_close was fixing the problem on older builds with PHP 7, but that benefit was lost on PHP 8.x

Setting CURLOPT_FORBID_REUSE on the connection handle before doing curl_exec() appears to fix it. This prevents the connection from attempting to reuse the same TCP connection for later calls to cURL.

It's still not clear why this only seems to affect the save+force update code path, but it's a better behavior overall anyhow.

Commit coming shortly.

I can also confirm the recent changeset fixes the issue in 2.7.0 snapshots.