mirror of
https://github.com/qdm12/ddns-updater.git
synced 2026-08-02 10:38:41 -04:00
Bug: Godaddy is bad #54
Assignees
saavagebueno
Clear assignees
saavagebueno
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/ddns-updater#54
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @oozj on GitHub (Aug 6, 2020).
Originally assigned to: @qdm12 on GitHub.
2020-08-06T15:21:03.055Z ERROR HTTP status 401 - Unauthorized : Could not authenticate API key/secret
@qdm12 commented on GitHub (Aug 6, 2020):
Are you sure your API secret is valid?
@jpherrell commented on GitHub (Aug 7, 2020):
I'm having the same issue. I can access the API myself using Postman and the same keys. Doesn't fail if there is nothing to update, but does if there is a change.
@qdm12 commented on GitHub (Aug 7, 2020):
Ok I'll check, maybe they changed their API. Should be done tomorrow.
@qdm12 commented on GitHub (Aug 9, 2020):
Hello both, I checked and their API did not change wether to update DNS records or for authorization.
Unfortunately, I have no domain at GoDaddy anymore, can you please try
Replacing:
[KEY]by your API Key[SECRET]by your API secret[DOMAIN]by your domain@by your host (or subdomain)And see/report back the response? That should update your record to 127.0.0.1 (nothing really). That should work according to Godaddy's doc and ddns-updater should do the exact same.
@jpherrell commented on GitHub (Aug 19, 2020):
Sorry it has taken so long for me to reply:
When I send a body of {"data":"127.0.0.1"} I get this from them:
{
"code": "INVALID_BODY",
"fields": [
{
"code": "UNEXPECTED_TYPE",
"message": "is not a array",
"path": "records"
}
],
"message":
"Request body doesn't fulfill schema, see details in
fields"}
When I send a body of
[
{
"data": "127.0.0.1",
"name": "@",
"ttl": 3600,
"type": "A"
}
]
it works fine.
On Sun, Aug 9, 2020 at 9:24 AM Quentin McGaw notifications@github.com
wrote:
@qdm12 commented on GitHub (Aug 19, 2020):
👍 That should be it, will fix it tonight. Thanks for answering back!
@qdm12 commented on GitHub (Aug 19, 2020):
Actually the program already sends
[{"data":"127.0.0.1"}]as the body, can you try with just that body?Referring to their API documentation, precisely to https://developer.godaddy.com/doc/endpoint/domains#/v1/recordReplaceTypeName, it seems only
"data"is required in the body of the request;"name'and"type"are given in the URL.Sorry I have no domain with GoDaddy so I'm a bit blind sighted for debugging it.
@jpherrell commented on GitHub (Aug 20, 2020):
I tried it with just [{"data": "127.0.0.1"}] and it worked as well. I'll
get the latest ddns-updater image and try another test run later today.
On Wed, Aug 19, 2020 at 9:46 PM Quentin McGaw notifications@github.com
wrote:
@qdm12 commented on GitHub (Sep 14, 2020):
Hey sorry for being away for a while, but is it working again perhaps? If not, what's the error log message you get? Still an authentication error? Thanks!
@jpherrell commented on GitHub (Sep 14, 2020):
Sorry, it wasn't working last time I tried the latest code. Seems like it
was still an auth issue. Perhaps it's in the handling of the config string
that I'm passing to the container. Not sure.
Since I'm a developer myself, I wrote my own updater. So I haven't tried to
figure out what the issue was.
Sorry I can't be of any more help,
Jon
On Mon, Sep 14, 2020, 7:53 PM Quentin McGaw notifications@github.com
wrote:
@qdm12 commented on GitHub (Sep 20, 2020):
Alright thanks for letting me know. Actually what's your script out of curiosity regarding the authorization part?
My code sets as header
Authorization: sso-key [KEY]:[SECRET]are you using something different?And @oozj did you manage to make it work perhaps?
@jpherrell commented on GitHub (Sep 23, 2020):
My code is in Python/Django, but you'll get the point. I think we're doing
the same thing. I really think it's something I was doing setting the
parameters for the container.
os.environ.get('GO_DADDY_DOMAIN', '') + "/records/A/@"
go_daddy_headers = {'Content-Type': 'application/json',
'Authorization': 'sso-key
{0}:{1}'.format(os.environ.get('GO_DADDY_KEY', ''),
os.environ.get('GO_DADDY_SECRET', ''))}
body = [{"data": self.current_address}]
response = requests.put(self.go_daddy_url,
headers=self.go_daddy_headers, json=body)
On Sun, Sep 20, 2020 at 6:04 PM Quentin McGaw notifications@github.com
wrote:
@qdm12 commented on GitHub (Sep 23, 2020):
Nice thanks a lot for sharing, I'll cross compare to ensure we have the same thing 😄
@qdm12 commented on GitHub (Sep 23, 2020):
Thanks again for sharing. It is indeed exactly the same 😄 Let's close the issue unless someones encounters the problem again. Did you have any funny characters in your key or secret perhaps?
@jpherrell commented on GitHub (Sep 23, 2020):
I thought of that. Mostly alphanumeric, and nothing that would require
escaping.
On Wed, Sep 23, 2020, 9:12 PM Quentin McGaw notifications@github.com
wrote: