DDNS Updater | Password is not valid

Apps and Virtualization
,
1

Hello,

On TrueNAS Scale I installed the “ddns updater” official application. After set the config, I deploy the app. But it’s stuck on deploying and when I read the log it says that the password is not correct, see below.

ddns updater log

  • INFO reading JSON config from environment variable CONFIG
  • ERROR configuration given: password is not valid: password “my password” does not match regex "^[a-f0-9]{32}$"
  • INFO Shutdown successful

My domain is hosted by www.namecheap.com.
The password I created on there site, is the password I set in the app config.
Current TrueNAS version: Dragonfish-24.04.2

Please can somebody help me with above, so the application will deploy and do his thing?

Best regards
Philomath

My Server Setup

  • Case: Jonsbo N4
  • Mobo: ASUS Pro WS W680M-ACE SE
  • RAM: 2x Kingston KSM48E40BD8KM-32HM
  • CPU: Intel Core i7-14700K
  • Disk: storage: 4x Toshiba MG Series 3.5" 22 TB SATA
  • SSD: Cache: WD Red SN700 1TB
  • SSD: Opp Sys: WD Red SN700 500GB
  • PSU: Cooler Master V1100 SFX Platinum
  • NIC: ASUS XG-C100C V2
2

Please post the settings for this app here so we can see the details of your ddns-updater configuration.

3

Looks like your password “my password” includes a space character and the regex checker does not allow for spaces. Looks like it only allows 32-character alphanumeric passwords.

1 Like
4

Are you using the correct password?

You are supposed to use the very specific dynamic dns password that Namecheap can generate for you, like can be seen in the documentation for the app:

1 Like
5

Additionally, I don’t know how namecheap does it, but a few of DDNS providers I’ve used never actually used the actual account password. Rather, it uses something like API token or maybe client_secret or something similar, which you usually can get out of your account dashboard.

6

That is essentially what Namecheap is doing, by breaking out the dynamic DNS and giving access to it by use of the specific password. They don’t call it API access though.

Any service that expects you to use your primary login info for something like this, thus potentially giving access to everything else in your account, is not security minded.

7

Hello,

First of all thank you to everyone who responded to help me, and others reading this.

As @neofusion mentioned, I had to make this possible trough the option dynamic DNS feature in Namecheap. I followed the steps from GitHub (enable the option) to accomplished correct working of the DDNS Updater app. My current experience in this is somewhat limited, so I had not understood this method.

The password is an 32 long string (that @Whattteva mentioned earlier) from the DDNS feature, and I entered this in the app config. After saved the new settings, everything is working correctly.

Besides the fact that it all works well, I still have an error code in the app shell when I open it. Should I be concerned about the following?

Error code from app Shell

error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec “e175c7f1977a314852a47eb0ecba2259af35a11a1066b1dbf2124e333c27709f”: OCI runtime exec failed: exec failed: unable to start container process: exec: “/bin/sh”: stat /bin/sh: no such file or directory: unknown

Btw, don’t know exactly how to share easily the config of the application. Let me know if there some way if needed. Very useful for research indeed Protopia :wink:

Best regards
Philomath

8

I get the same error if I try to open a shell inside the container.

It looks like the image used for this app doesn’t include a shell executable.

1 Like
9

Hello Protopia,

Thank you for verify. Than I know it’s normal behavior.