You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. I used inadyn with dynu.com for a long time, but eventually some time ago it stopped working. Looking at updating my router (and inadyn version), it seems unchanged.
This may be a question, rather than a issue to be fixed, but I had suspected inadyn used the legacy (aka v1) API, which dynu notes is no longer supported.
But, I see issue #478 which is only a few months ago, which makes me fear my issue may be human error.
I'm getting a 200 response, with content "badauth". It looks from debug that it's doing HTTP Basic auth, which I'm 90% sure is no longer supported. Right now I'm seeing this in 2.8.1, but I don't think the code used for dynu.com has changed substantially, has it? I can test 2.12, I'll do that to verify.
The text was updated successfully, but these errors were encountered:
I opened a support request with dynu. Their docs still include many statements about the more traditional update methods, and even include a ddclient conf file which also reports an auth failure if I try to use it. So. Updates here welcome, but I think it may be a "they changed something" issue and I'll come back after I hear from them.
Hello. I used inadyn with dynu.com for a long time, but eventually some time ago it stopped working. Looking at updating my router (and inadyn version), it seems unchanged.
This may be a question, rather than a issue to be fixed, but I had suspected inadyn used the legacy (aka v1) API, which dynu notes is no longer supported.
But, I see issue #478 which is only a few months ago, which makes me fear my issue may be human error.
I'm getting a 200 response, with content "badauth". It looks from debug that it's doing HTTP Basic auth, which I'm 90% sure is no longer supported. Right now I'm seeing this in 2.8.1, but I don't think the code used for dynu.com has changed substantially, has it? I can test 2.12, I'll do that to verify.
The text was updated successfully, but these errors were encountered: