Deprecate the Infomaniak protocol - it now uses DynDns2
LenardHess opened this issue · comments
In #592 there already was the hint added to the config to use dyndns2 provider for Infomaniak instead.
The Infomaniak FAQ also suggests using dyndns2.
For reference, the infomaniak protocol still updates the IP address even if the response is treated as a failure:
ddclient[25190]: WARNING: Unknown reply from Infomaniak: HTTP/2 200
ddclient[25190]: WARNING: cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0, no-cache
ddclient[25190]: WARNING: content-type: text/plain; charset=UTF-8
ddclient[25190]: WARNING: date: Mon, 10 Jun 2024 23:19:10 GMT
ddclient[25190]: WARNING: expires: Thu, 19 Nov 1981 08:52:00 GMT
ddclient[25190]: WARNING: pragma: no-cache
ddclient[25190]: WARNING: server: Apache
ddclient[25190]: WARNING: set-cookie: PHPSESSID=<redacted>; path=/
ddclient[25190]: WARNING: set-cookie: IsExTaxPreference=1; expires=Tue, 11-Jun-2024 23:19:07 GMT; Max-Age=86400; path=/; domain=infomaniak.com
ddclient[25190]: WARNING: set-cookie: hosting_session=<redacted>
ddclient[25190]: WARNING: vary: Accept-Encoding
ddclient[25190]: WARNING: content-length: 19
ddclient[25190]: WARNING: strict-transport-security: max-age=63072000
ddclient[25190]: WARNING:
ddclient[25190]: WARNING: good xxx.xxx.xxx.xxx
ddclient[25247]: WARNING: curl cannot connect to https://infomaniak.com using IPv0
ddclient[25248]: FAILED: updating <redacted>: could not update IP on Infomaniak
ddclient[25254]: WARNING: skipping update of <redacted> from <nothing> to xxx.xxx.xxx.xxx.
ddclient[25254]: WARNING: last updated <never> but last attempt on Tue Jun 11 01:18:59 2024 failed.
@davidebeatrici Thanks for reporting. #692 should fix that bug.
You're welcome, thank you for the fix.