https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162022-02-25T03:07:55ZpfSense bugtrackerpfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=593512022-02-25T03:07:55ZViktor Gurov
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li><li><strong>Priority</strong> changed from <i>Very High</i> to <i>Normal</i></li><li><strong>Target version</strong> deleted (<del><i>22.01</i></del>)</li></ul><p>This site is not for support or diagnostic discussion.</p>
<p>For assistance in solving problems, please post on the <a href="https://forum.netgate.com" class="external">Netgate Forum</a> or the <a href="https://www.reddit.com/r/pfSense/" class="external">pfSense Subreddit</a> .</p>
<p>See <a href="https://docs.netgate.com/pfsense/en/latest/development/bug-reports.html" class="external">Reporting Issues with pfSense Software</a> for more information.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=593532022-02-25T04:17:04ZDanilo Zrenjanin
<ul></ul><p>Tested on the:<br /><pre>
2.6.0-RELEASE (amd64)
built on Mon Jan 31 19:57:53 UTC 2022
FreeBSD 12.3-STABLE
</pre></p>
<p>I replicated the issue. After finishing the DynDNS setup using CloudFlare service and clicking the <strong>Save</strong> or <strong>Save & Force Update</strong> it will not bring you back to the /services_dyndns.php page. After some time you will get <strong>504 Gateway Time-out</strong>. But in my case, the settings were applied and the IP address got updated correctly.</p>
<p>After simulating the public IP address change the service pushed the new address to Cloudflare without any issues.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=593542022-02-25T04:18:15ZDanilo Zrenjanin
<ul><li><strong>Status</strong> changed from <i>Rejected</i> to <i>New</i></li></ul> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=593552022-02-25T04:36:04ZDanilo Zrenjanin
<ul></ul><p>Here are related logs:<br /><pre>
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"
</pre></p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=593562022-02-25T04:41:23ZHong Duong Pham
<ul></ul><p>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.<br />With google domain, the service completely not update the IP address. I take the issue after upgrade pfsense to version 2.6.0</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=604042022-04-15T20:38:53ZKris Phillips
<ul></ul><p>Hong Duong Pham wrote in <a href="#note-5">#note-5</a>:</p>
<blockquote>
<p>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.<br />With google domain, the service completely not update the IP address. I take the issue after upgrade pfsense to version 2.6.0</p>
</blockquote>
<p>Hello,</p>
<p>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.</p>
<p>Please provide supporting documentation.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=604122022-04-16T09:14:23ZHong Duong Pham
<ul></ul><p>Logs is the same reply from Danilo Zrẹnanin. Please check !</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=609432022-05-06T17:04:58ZSteve Wheeler
<ul><li><strong>Subject</strong> changed from <i>Dynamic DNS on Pfsense was not worked</i> to <i>Dynamic DNS client fails to complete.</i></li><li><strong>Target version</strong> set to <i>2.7.0</i></li><li><strong>Affected Plus Version</strong> set to <i>22.01</i></li></ul><p>We replicated this on a customer firewall using Cloudflare dyndns.</p>
<p>At boot the client comes up correctly and shows as up to date.</p>
<p>If you make a change, such as setting the dyndns client to a different WAN, and save/force_update the client seems to run correctly but the webpage never returns. With verbose logging enabled the system log shows the complete and successful update. <br />Eventually the page times out and shows a 504 error. After that it's no longer possible to trigger a dyndns update either from the gui or by a WAN update such as a gateway failover.<br />If you restart PHP it is then possible to trigger one further update. It appears something in the update process fails to complete and prevents further updates.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=611052022-05-12T11:10:14ZMarcos M
<ul><li><strong>Project</strong> changed from <i>pfSense Plus</i> to <i>pfSense</i></li><li><strong>Subject</strong> changed from <i>Dynamic DNS client fails to complete.</i> to <i>Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeout</i></li><li><strong>Category</strong> changed from <i>Dynamic DNS</i> to <i>Dynamic DNS</i></li><li><strong>Affected Plus Version</strong> deleted (<del><i>22.01</i></del>)</li><li><strong>Plus Target Version</strong> set to <i>22.05</i></li><li><strong>Affected Version</strong> set to <i>2.6.0</i></li><li><strong>Affected Architecture</strong> <i>All</i> added</li><li><strong>Affected Architecture</strong> deleted (<del><i>amd64</i></del>)</li></ul> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=611072022-05-12T11:10:34ZMarcos M
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-1 status-11 priority-4 priority-default closed" href="/issues/12900">Bug #12900</a>: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeout</i> added</li></ul> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=612412022-05-17T16:49:16ZJim Pingle
<ul><li><strong>Assignee</strong> set to <i>Jim Pingle</i></li></ul><p>I can reproduce this in my lab with Namecheap as well.</p>
<p>I added some debug logging and it seemed to be getting caught up on <code>curl_close()</code> but commenting out the calls to that didn't help so it's not just that. I'll try to at least narrow it down further.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=612442022-05-18T10:38:14ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>Seems to be a problem with multiple overlapping curl requests. It doesn't like making new requests when there is one still hanging out unclosed. Not too hard to work around in this case since it isn't really necessary to keep it open the way it is currently being handled.</p>
<p>I have a fix ready, will be in shortly.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=612472022-05-18T11:15:52ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Fixed in <a class="changeset" title="Close earlier to avoid overlap. Fixes 12870 Gather the information we need from curl and close t..." href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/bdffb77d1aa21770b23ef408ad9fba79d0825ec5">bdffb77d1aa21770b23ef408ad9fba79d0825ec5</a></p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=612622022-05-19T08:22:06ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>I can't reproduce this on any of my Namecheap entries on today's snapshot with the fix in place. Looks good to me.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=613562022-05-24T07:16:41ZChris Swinney
<ul></ul><p>Jim Pingle wrote in <a href="#note-14">#note-14</a>:</p>
<blockquote>
<p>I can't reproduce this on any of my Namecheap entries on today's snapshot with the fix in place. Looks good to me.</p>
</blockquote>
<p>This is great @jim. Are there any plans for a v26.1 dot release, or is this only going to make it to v27?</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=613582022-05-24T07:26:16ZJim Pingle
<ul></ul><p>No plans for a point release at this time.</p>
<p>You can install the <a href="https://docs.netgate.com/pfsense/en/latest/development/system-patches.html" class="external">System Patches package</a> and then create an entry for <code>bdffb77d1aa21770b23ef408ad9fba79d0825ec5</code> to fetch and apply the fix. I may add that into the recommended patches list for 2.6.0/22.01 as well.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=640522022-11-26T10:25:07ZDean Arnold
<ul></ul><p>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.</p>
<p>Will this appear fix become part of 2.7 in an upcoming Devl build and/or the full release?</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=640772022-11-28T07:57:52ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>New</i></li><li><strong>% Done</strong> changed from <i>100</i> to <i>0</i></li></ul><p>The fixes should already be in 23.01/2.7.0 snapshots, but it's possible some other change broke this again.</p>
<p>I can reproduce it here as well with Namecheap. It updates but the GUI never returns from the action, like it's still being held open again.</p>
<p>I'll take another look.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=640882022-11-28T11:36:29ZJim Pingle
<ul></ul><p>I think I have this fixed again, it's still weirdness in cURL.</p>
<p>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</p>
<p>Setting <code>CURLOPT_FORBID_REUSE</code> on the connection handle before doing <code>curl_exec()</code> appears to fix it. This prevents the connection from attempting to reuse the same TCP connection for later calls to cURL.</p>
<p>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.</p>
<p>Commit coming shortly.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=640892022-11-28T11:40:09ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="DDNS Save+Force timeout improvements. Fixes #12870 * In PHP8, curl_close is a no-op, so remove i..." href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/02d6ca03965777ab95da05c7ae526aa75d2ddc2a">02d6ca03965777ab95da05c7ae526aa75d2ddc2a</a>.</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=641342022-11-30T18:01:17ZMarcos M
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-1 status-11 priority-4 priority-default closed" href="/issues/13600">Bug #13600</a>: Saving a DDNS entry can lead to the GUI timing out.</i> added</li></ul> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=641362022-11-30T18:02:36ZMarcos M
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>The fix worked for me, thanks!</p> pfSense - Bug #12870: Clicking Save & Force Update on a Dynamic DNS entry results in a GUI timeouthttps://redmine.pfsense.org/issues/12870?journal_id=642762022-12-07T00:45:49ZDean Arnold
<ul></ul><p>I can also confirm the recent changeset fixes the issue in 2.7.0 snapshots.</p>