desec and os-ddclient error failed to set new ip

[klockxd]

Hello,
I have recently switched to opnsense and I've been trying to setup dynamic dns using the os-ddclient plugin. I am using desec-v4 and have setup api keys properly and put the hosts. However, it seems that it does nothing and looking at the log files I see the following error:
Account ______ [custom - ] failed to set new ip [desec-v4 - ]
I have tried using custom instead of desec-v4 and it results in the same. If anyone can help how I can go about troubleshooting this. Thank you very much.

[klockxd]

I'd like to add that if the subdomain already exists with an A record in Desec, it just ends up deleting it.

[cookiemonster]

try with service: custom ; protocol: DynDNS 2. That is what I've had for some time without problems.
I did set it a while ago and I don't think I ever tried with desec-v4 so I couldn't tell if it was meant to be done that way.

[klockxd]

Using custom, the logs are more nice but still I don't see any updated dns entries in desec. It in fact deletes what I had previously, as mentioned before.
2024-12-23T09:34:50    Notice    ddclient    Account ___ [custom - ] not modified   
2024-12-23T09:34:41    Notice    ddclient    Account ___ [custom - ] executing
2024-12-23T09:33:00    Notice    ddclient    Account ___ [custom - ] updated   
2024-12-23T09:33:00    Notice    ddclient    Account ___ [custom - ] set new ip [good]   
2024-12-23T09:32:51    Notice    ddclient    Account ___ [custom - ] executing   
2024-12-23T09:32:51    Notice    ddclient    Account ___ [custom - ] uses DynDNS2 for service

[cookiemonster]

2024-12-23T09:33:00    Notice    ddclient    Account ___ [custom - ] set new ip [good]   
2024-12-23T09:32:51    Notice    ddclient    Account ___ [custom - ] executing   
2024-12-23T09:32:51    Notice    ddclient    Account ___ [custom - ] uses DynDNS2 for service

This suggests your ip now is up date. What are you missing and where?

[klockxd]

The ip is not being updated in desec. It showed those logs the first time I think because it deleted the entry I had in desec before but after it has that deleted it doesn't set the new ip and gives the following error:
2024-12-25T12:21:08   Error   ddclient   Account ____ [custom - ] failed to set new ip [404 - nohost]

[cookiemonster]

Works for me so maybe a problem on the desec side but I couldn't tell you what. Sorry.
If you maybe find out something from them, then I'll be happy to share what I have on my side.