DynDNS Update Fails with KeyError: 'value'

Support
, ,
1

What type of hardware are you using: Old laptop or computer
What YunoHost version are you running: 12.1.7.1
How are you able to access your server: The webadmin
SSH
Direct access via physical keyboard/screen

Describe your issue

Hello everyone,

I am facing a persistent issue where my DynDNS update for my domain xx.noho.st fails with a KeyError: ‘value’. I have performed extensive troubleshooting, and the problem still persists, pointing to a deeper configuration issue.

  1. Problem Description
    When I run yunohost dyndns update --force, the operation fails with the following traceback:

Bash

Traceback (most recent call last):
…
File “/usr/lib/python3/dist-packages/yunohost/dyndns.py”, line 499, in dyndns_update
if record[“value”] == “@”:
KeyError: ‘value’
This error also occurs when I run other DNS-related commands.

I have discovered that the root cause is a missing file: /etc/yunohost/dyndns/dyndns_conf.json. This file does not exist, which causes the scripts to fail.

  1. Troubleshooting Steps
    I have already taken the following steps:

Confirmed my YunoHost version is 12.1.7.1.

Performed a reinstall of the core yunohost package using sudo apt install --reinstall yunohost.

Despite these fixes, the KeyError persists, and the DynDNS update cannot be completed.

  1. Log File
    Here is the log from the most recent failed DynDNS update:
    https://paste.yunohost.org/raw/dadigayuri

I would appreciate any assistance in investigating this further. Thank you!

Share relevant logs or error messages

https://paste.yunohost.org/raw/dadigayuri

2

It’s a known issue in latest testing version, thanks for to info anyway :slight_smile:

I think it’s already fixed and it will be fixed in next YunoHost update.

1 Like
3

Thanks a lot for the quick reply! It’s great to hear that the bug is a known issue and a fix is on the way.

I’ve got a quick question for you: Since the dyndns update command isn’t quite working for me yet—it thinks nothing needs to be updated even when my IP has changed—is there a way to manually force the IP to update in the meantime?

I just want to make sure my domain stays online until the bug fix arrives.

Cheers!