Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

badauth when trying to use DynDNS API #54

Open
RHuehne opened this issue Jul 24, 2020 · 3 comments
Open

badauth when trying to use DynDNS API #54

RHuehne opened this issue Jul 24, 2020 · 3 comments

Comments

@RHuehne
Copy link

RHuehne commented Jul 24, 2020

Hi There,

The update via Web is working - but actually only over the

http(s)//example.com/update?secret=[SHARED_SECRED]&domain=[HOSTNAME]&addr=[IP] url.

When using /v2/update I'm getting a badauth back in the browser, even if i use the following auth method.

http(s)://fakeUser:[SHARED_SECRED]@example.com/v2/update?hostname=[HOSTNAME]&myip=[IP]

in the Log:
2020/07/24 19:07:14 Invalid shared secret:

Am I doing something wrong, or is this basic-auth feature which the Dyn-compatible url uses not working anymore??
Sadly I think I will need this working, if I want to use it with some zywall device....

Cheers, Rainer

@dstapp
Copy link
Owner

dstapp commented Jul 26, 2020

Hey, can you try setting a password with no special chars, just once for testing and see if it's at least printed in the logs?

@0verEngineer
Copy link

I had the same Problem and i uused a password with no special chars.

@thomas-mc-work
Copy link

Seems like the API for the DynDNS compatible API endpoints is a bit different. You can test it with this curl command:

curl -su "karl:s3cr3t" "https://ddns.myhost.org/v3/update?hostname=test1&myip=99.99.99.99"

The auth data has to be provided via basic auth. I hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants