mirror of
https://github.com/qdm12/ddns-updater.git
synced 2026-08-02 18:48:49 -04:00
TrueNAS charts generate json config with results parent key #438
Assignees
saavagebueno
Clear assignees
saavagebueno
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/ddns-updater#438
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RebelliousX on GitHub (Sep 19, 2024).
v2.8.0 broke FreeDNS, I can't use it with v1 dynamic update interface or the new v2 dynamic interface I get empty results in the WebUI. In v2.7.0 I used the token from v1 dynamic update interface, didn't change that and it worked fine. Since 2.8.0 broke things, I tried the new token for v2, same thing.
v2.7.0 is working fine, I am using TrueNAS Scale 24.10 beta1. I didn't change any settings when I upgraded from 2.7.0 to 2.8.0.
It seems and I am not sure, the config file is empty?!Here is the container log from Portainer. Note that I installed DDNS-Updater from TrueNAS App section, not from Portainer itself, I just used portainer to grab the logs.
@qdm12 commented on GitHub (Sep 19, 2024):
Found no setting to update record- that's odd. Try deleting and recreating the container? What's the content of your config json file?@RebelliousX commented on GitHub (Sep 19, 2024):
@qdm12 I did that multiple times, rebooted the system, nothing. I tried the old token for v1 dynamic update and v2, same thing.
I updated the original post with a screenshot of
config.jsonfile, so it seems valid. I am still struggling how to copy/paste from shell webui from truenas, lol.But according to the freedns settings. Is the
resultdictionary okay to be there in the screenshot above? I don't know.@qdm12 commented on GitHub (Sep 19, 2024):
Try running with
LOG_LEVEL=debug? It should log out your JSON configuration, does it look like it matches what you show?Let's not focus on freedns, it just looks like ddns-updater does not find any configuration to use, so it's not even aware it should update anything (freedns or not).
@RebelliousX commented on GitHub (Sep 19, 2024):
@qdm12 Thank you for your help. I added LOG_LEVEL=DEBUG as environment variable and here is the log. (I removed personal details like the exact subdomain and token), it matches the settings.
Things I tried too:
ix-volumegenerated by TrueNAS.Same thing.
And the WebUI:
@qdm12 commented on GitHub (Sep 19, 2024):
Oh the top most key should be settings, not results. I'm not sure where you read about results or warnings.
@RebelliousX commented on GitHub (Sep 19, 2024):
@qdm12 Exactly. It gets generated by TrueNAS somehow, like I said, I even edited the config file manually using nano editor, it reverts back with
resultsdictionary or hashmap or whatever it is called. Also please look at the UMASK, is it correct, I see only writes, I am not sure?On another issue, I lost the ability to rollback to the previous container version from TrueNAS WebUI, since I deleted the app while testing things. Now I am kind of stuck. I tried to use Portainer to create new stack with docker compose and install version 2.7.0.
I used the docker compose template in the main page. Modified the environment variable
The issue I get error that permission denied can't read config.json file. I even gave the container SYS_ADMIN privileges.
When installing the app normally through TrueNAS web interface, I know the UID should be 1000, but when TrueNAS tries to install the app, it wants UID=568 which I believe the built-in
appsuser if I am not mistaken. And that always worked fine.Any suggestions?
Edit:
If I delete the volume it bypasses the error, and the webui shows the correct results.That works even on 2.8.0. But that means, any settings can't be saved per the ReadMe on the main page.
I deleted the BIND and created a new empty volume and gave it a name, changed the volume mapping from BIND to Volume and the path
/updater/datafor its value. As for theHostvalue, changed it from/data/compose/13/dataand I pointed it towards the new created volume.Now the output log:
With this, it works with latest version 2.8.0.
But this is not a real solution, this is just a band-aid if you will. I think there might be a need to modify the way
settingskey is read. That is, if it is not found, then we need to loop through any keys in the JSON and get their values untilsettingskey is found. That will solve the problem for sure. I hope you implement this.@qdm12 commented on GitHub (Sep 20, 2024):
Not exactly sure what you mean, but I made a v2.8.1 release fixing the umask behavior. It would work fine more or less on v2.8.0 though.
Actually that would be a band aid solution 😄 What is creating that JSON file with the
resultsandwarningskeys? That's where the problem is. I would guess it's truenas charts repository, so please create an issue on https://github.com/truenas/charts/issues/new so that they fix that json configuration file generation.@RebelliousX commented on GitHub (Sep 20, 2024):
@qdm12 True, I guess both solutions are band aids. I created a new issue in TrueNAS charts. I would like to keep this open until it gets fixed if you don't mind, I will close it then. Thanks for your help.
This is getting fixed here https://github.com/truenas/apps/pull/469
Thanks @qdm12 for your help.
@haldi4803 commented on GitHub (Jan 2, 2025):
It's not fixed....
but every time the container starts it creates a new "config.json" file and overwrites the one i created.