ddclient: Protocol is used twice on query

[Hunv]

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

• I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
• I have searched the existing issues, open and closed, and I'm convinced that mine is new.
• The title contains the plugin to which this issue belongs

Describe the bug
After changing to another Dynamic DNS provider (dnshome.de), I tried to configure the new one.
I configured the following parameters:
Service: Custom
Protocol: Custom PUT
Server: https://www.dnshome.de/dyndns.php?ip=__MYIP__
Username:
Password:
Hostnames:
Check IP method: Interface
Interface to monitor: My Internet Gateway Interface
Force SSL: true

After that didn't work, I checked to logs. I see the following line in the Logs:
SENDING: url="https://https://www.dnshome.de/dyndns.php?ip=__myip__/nic/update?system=dyndns&hostname=<my domain>&myip=<my internet IP>"
As <my internet IP> shows my real IP, that is working, but what confuses me is the https://https:// at the beginning. The next log line is: WARNING: CURL error (6) Couldn't resolve host. The given remote host was not resolved.. And that also seems to be because of the double-https:// at the beginning.

I tried to remote the "https://" from the Server-Field, but then I cannot save as it states, that I need to put a valid Address in the field.
I also tried disabling the "Force SSL" option, but the issue stays almost the same. Only the first https:// changes to http://.

I think I am not doing anything wrong, so I think this is a bug.

Environment
OPNsense 25.7.10-amd64
os-ddclient 1.28

[carepack]

Hi, also experiencing this behaviour. The sending url looks strange with https://http:// in front and is also for me the case. Wasn't abel to solve via reinstall the plugin or other ways.

[jnikodemus]

Did you try the custom method of the "native" backend?

[carepack]

All attempts with native weren't unsuccessfully. I wasn't able to get it working with the native backend also in previous opnsense versions. ddclient was the only backend were setup was successful.

Maybe other were able to get it working with native backend?

[jnikodemus]

After investigating the issue with the custom provider in the ddclient backend, it appears the problem occurs because the server field validation and the “Force SSL” checkbox are used together. Each of them would work fine on its own: the server field accepts a protocol as expected, and the “Force SSL” option correctly enforces the intended protocol later on. But both enforce a protocol prefix and the protocol ends up being added twice (e.g., https://https://...), which leads to the duplication.

[carepack]

In my case the checkbox force ssl isn't ticked.
An before the upgrade to 25.xx everything was working and in the logs the url has shown correct as http://provider.xyz.
But maybe got you wrong? Thx.

[jnikodemus]

My tests showed that if you check the "Force SSL" there will be "https://" prefixed to your "Server" string. If its not checked, it will prefix "http://" to your "Server" string. Problem seems to be, that you can't save a "Server" string without protocol. If the "Server" field wouldn't check for a protocol, your specific problem should be solved. In my tests i removed the check and the duplicate protocol was gone.

[carepack]

Perfect! Thx a lot!