Bug 12195

Summary: freedns.afraid.org update error
Product: DDNS Updater Reporter: phane7
Component: ProvidersAssignee: Stefan Schantl <stefan.schantl>
Status: CLOSED NOTABUG QA Contact: Michael Tremer <michael.tremer>
Severity: Major Usability    
Priority: - Unknown - CC: jonipfir
Version: unspecifiedFlags: stefan.schantl: needinfo+
Hardware: all   
OS: All   
Attachments: freedns.afraid.org example

Description phane7 2019-09-29 18:38:42 UTC
Recently, freedns.afraid.org ddns updates fail.

Thread from forum discussing the problem is below

https://forum.ipfire.org/viewtopic.php?f=27&t=23406

Three confirmed users have this issue.  The only error that shows up in logs that we can find is below:

DDNSUpdateError: The update could not be performed

The issue started for me on 8/09/2019, another user reported the problem starting for them on 08/31 and the third just started having the issue after trying to replicate the problem on their end to troubleshoot it.
Comment 1 Michael Tremer 2019-09-30 08:44:44 UTC
It looks like the update URL has changed.

If anyone could confirm that, this would be a one-line change.
Comment 2 Jon 2019-10-16 02:41:22 UTC
Created attachment 712 [details]
freedns.afraid.org example

see examples at bottom of attachment
Comment 3 Jon 2019-10-16 02:42:47 UTC
Comment on attachment 712 [details]
freedns.afraid.org example

https://freedns.afraid.org/dynamic/update.php?<USERNAME>

Information:
https://freedns.afraid.org/dynamic/

Check:
https://freedns.afraid.org/dynamic/check.php
Comment 4 Stefan Schantl 2019-11-05 18:06:01 UTC
Hello registered a new account on freedns.afraid.org and performed a test - Everything worked without any modifications:

Opening database /var/lib/ddns.db
Initialising database layout
Sending request (GET): https://checkip6.dns.lightningwirelabs.com
Request-Header:
  Pragma: no-cache
  User-agent: IPFireDDNSUpdater/012
Sending request (GET): https://checkip4.dns.lightningwirelabs.com
Request-Header:
  Pragma: no-cache
  User-agent: IPFireDDNSUpdater/012
Header der Antwort (Status Code 200):
  content-length: 35
  strict-transport-security: max-age=31536000; includeSubDomains; preload
  vary: Accept-Encoding
  connection: close
  etag: "b35dd6ff36e747125869f4c99c0098d3a21f16cf"
  date: Tue, 05 Nov 2019 18:00:30 GMT
  content-type: text/html; charset=UTF-8
Eine Aktualisierung für ipfiretest.strangled.net  (freedns.afraid.org) wird aufgrund einer IP-Adress Änderung vorgenommen
Sending request (GET): https://freedns.afraid.org/dynamic/update.php?mysecrettoken&address=127.0.0.1
Request-Header:
  Pragma: no-cache
  User-agent: IPFireDDNSUpdater/012
Header der Antwort (Status Code 200):
  x-cache: MISS
  transfer-encoding: chunked
  expires: Mon, 26 Jul 1997 05:00:00 GMT
  vary: Accept-Encoding
  server: nginx
  connection: close
  pragma: no-cache
  cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  date: Tue, 05 Nov 2019 18:00:32 GMT
  content-type: text/plain; charset=utf-8
Dynamic DNS-Update für ipfiretest.strangled.net  (freedns.afraid.org) erfolgreich
Logging successful update for ipfiretest.strangled.net 

Please confirm this is no configuration issue and the problem still exists.
Comment 5 phane7 2019-11-05 19:51:56 UTC
It's still not working on my end.  The only configuration options are the domain, login and password.  I know these are correct.  However, the update URL in your script looks like it's using the token and not the login.  I'll try using the update token for the login and password blank (since it wouldn't be needed with the token) and see if that works.

IP Fire has me locked out of updates until tomorrow morning so I'll have to wait until then to see if that works.
Comment 6 Stefan Schantl 2019-11-06 08:19:58 UTC
Regarding to our documentation on the wiki, the token should be placed in the username field and the password be blank.

https://wiki.ipfire.org/configuration/services/dyndns_providers
Comment 7 phane7 2019-11-06 10:17:35 UTC
It's working now.  I don't know when that changed because for years I had the actual login and password there and it was working until 8/09/19.