Created attachment 915 [details] DDns IPFire configuration. Steps to reproduce the issue: 1. The IPFire DDns module is accessed. (see photo 1) 2. The corresponding ddns is created in "nsupdate.info". (see photo 2) 3. The "hostname" and "token" fields are filled with the data generated in nsupdate.info and when accepting the configuration, it gives an error: (see photo 3) Temporary solution: copy the configuration files from the path /var/ipfire/ddns to the computer to configure and modify the data by hand.
Created attachment 916 [details] (photo 1) DDns IPFire configuration.
Created attachment 917 [details] (photo 2) nsupdate.info configuration page.
Created attachment 918 [details] (photo 3) IPFire ddns error page.
You should probably not publish your tokens and change it now. Can you provide log files, please?
Hi Michael. I have re-reproduced the problem and it happens again every time. The bad thing is that I have looked in all the logs and I have not found anything. Regardless of whether you have found something or not, it is easily reproducible. Even if you make up the data, it should save the configuration without giving this error even if it gives update errors later.
(In reply to Roberto Peña from comment #5) > I have re-reproduced the problem and it happens again every time. The bad > thing is that I have looked in all the logs and I have not found anything. Could you please post them?
Hi Michael. I have not found anything in the LOGs. But if you want to try it, I put here a valid NSUpdate DDNs: Homepage: http://ipfire.org Go to: Services Dynamic DNS Enter the following data (and click ADD afterwards): Setting Value Service nsupdate.info Enabled (check) Host Name prueba.nsupdate.info User name prueba.nsupdate.info Password p9FwyMKpem You can try this with these data. Thanks.
Hello Roberto, a big thanks for your bug report and sharing your data for testing purposes. I've tested them on my IPFire (C158) system and everything worked fine. Aktualisierung von prueba.nsupdate.info erzwungen Sending request (GET): https://checkip6.dns.lightningwirelabs.com Request-Header: User-agent: IPFireDDNSUpdater/013 Pragma: no-cache Sending request (GET): https://checkip4.dns.lightningwirelabs.com Request-Header: User-agent: IPFireDDNSUpdater/013 Pragma: no-cache Header der Antwort (Status Code 200): content-length: 32 vary: Accept-Encoding etag: "1599071c1d241aab54d9cc14551c56d1194d4e08" date: Tue, 06 Jul 2021 16:11:15 GMT content-type: text/html; charset=UTF-8 strict-transport-security: max-age=31536000; includeSubDomains; preload connection: close Sending request (GET): https://nsupdate.info/nic/update?myip=xxx.xxx.xxx.xxx Request-Header: Authorization: Basic cHJ1ZWJhLm5zdXBkYXRlLmluZm86cDlGd3lNS3BlbQ== User-agent: IPFireDDNSUpdater/013 Pragma: no-cache Header der Antwort (Status Code 200): Server: nginx Date: Tue, 06 Jul 2021 16:11:15 GMT Content-Type: text/plain Content-Length: 17 Connection: close x-content-type-options: nosniff x-xss-protection: 1; mode=block X-Frame-Options: DENY Referrer-Policy: same-origin Vary: Accept-Language, Cookie Content-Language: en Strict-Transport-Security: max-age=31536000; Expect-CT: enforce, max-age=21600 Dynamic DNS-Update für prueba.nsupdate.info (nsupdate.info) erfolgreich Logging successful update for prueba.nsupdate.info
Hi Stefan. The problem is not with the update itself, but with the GUI that gives an error when trying to add it. If you select nsupdate.info provider, only appears "Hostname" and "Token". if you fill in those fields with prueba.nsupdate.info and Password, Above appears the error described. It only works if you copy the files from another IPFire and edit the files with the correct data. Once this is done, the update process works perfectly. In other words, in short. It is at the time of adding it in the GUI.
Created attachment 923 [details] Password not set error when you fill data in Hostname and Token field and push in ADD, appears these error, "Password not set."
See Password not set error image. Thanks.
Yeah, I got the same error yesterday as I entered your account details to test if they work with ddns. I already fixed that issue and send a patch to our develoment mailing list: https://patchwork.ipfire.org/project/ipfire/patch/20210706160829.2548-1-stefan.schantl@ipfire.org/ It hopefully will be shipped with Core 158 (if not to late for merging it) or in the meantime you can apply it manually to fix this WUI issue. PS: As it now is confirmed that nsupdate.info is working well, please change your authentication token to prevent abuse.
@Michael, please merge (if not to late) the patch from the above post into core 158. Thank in advance, -Stefan
Done. Thank you.
Thanks Stefan and Michael. It seems to be working properly. Now when adding it via GUI it no longer gives the error and it appears correctly. Thanks for your work and effort.
*** Bug 12659 has been marked as a duplicate of this bug. ***
Fix for this was implemented into Core Update 158 and this has been released. https://blog.ipfire.org/post/ipfire-2-25-core-update-158-released