starred/ddns-updater
1
0
Fork 0
mirror of https://github.com/qdm12/ddns-updater.git synced 2026-08-02 18:48:49 -04:00
Code Issues 312 Packages Projects Releases 10 Wiki Activity

Could not update ip address on godaddy and error "show HTTP status is not valid: 403: Authenticated user is not allowed access" #392

New Issue
Closed
opened 2025-11-20 04:23:30 -05:00 by saavagebueno · 10 comments
saavagebueno commented 2025-11-20 04:23:30 -05:00
Owner
Copy Link

Originally created by @Leoson0109 on GitHub (May 1, 2024).

Could not update ip address on godaddy and error "show HTTP status is not valid: 403: Authenticated user is not allowed access"

TLDR: Describe your issue in a one liner here

  1. Is this urgent: Yes
  2. DNS provider(s) you use: N/A
  3. Program version:Docker
  4. What are you using to run the container: docker-compose
  5. Extra information (optional)

Logs:

2024-05-01T15:02:27.406092772Z | stdout | 2024-05-01T15:02:27Z ERROR HTTP status is not valid: 403: Authenticated user is not allowed access
-- | -- | --
2024-05-01T15:02:26.816464273Z | stdout | 2024-05-01T15:02:26Z INFO Updating record [domain: elmostation.com \| host: @ \| provider: godaddy \| ip: ipv4] to use 42.2.41.218
2024-05-01T15:02:26.816236503Z | stdout | 2024-05-01T15:02:26Z INFO ipv4 address of elmostation.com is 112.118.68.250 and your ipv4 address  is 42.2.41.218
2024-05-01T15:02:26.457594503Z | stdout | 2024-05-01T15:02:26Z INFO [http server] listening on :8000
2024-05-01T15:02:26.457453936Z | stdout | 2024-05-01T15:02:26Z INFO [backup] disabled
2024-05-01T15:02:26.456761051Z | stdout | 2024-05-01T15:02:26Z INFO [healthcheck server] listening on 127.0.0.1:9999
2024-05-01T15:02:26.456350062Z | stdout | 2024-05-01T15:02:26Z INFO Reading history from database: domain elmostation.com host @ ipv4
2024-05-01T15:02:26.277442332Z | stdout | 2024-05-01T15:02:26Z INFO Found single setting to update record
2024-05-01T15:02:26.277368767Z | stdout | 2024-05-01T15:02:26Z INFO reading JSON config from environment variable CONFIG

Configuration file (remove your credentials!):

lastest

{"settings":[{"provider":"godaddy","domain":"elmostation.com","host":"@","key":"key","secret":"secret","ip_version":"ipv4","ipv6_suffix":""}]}

Host OS: docker

Originally created by @Leoson0109 on GitHub (May 1, 2024). Could not update ip address on godaddy and error "show HTTP status is not valid: 403: Authenticated user is not allowed access" **TLDR**: *Describe your issue in a one liner here* 1. Is this urgent: Yes 2. DNS provider(s) you use: N/A 3. Program version:Docker 4. What are you using to run the container: docker-compose 5. Extra information (optional) Logs: ``` 2024-05-01T15:02:27.406092772Z | stdout | 2024-05-01T15:02:27Z ERROR HTTP status is not valid: 403: Authenticated user is not allowed access -- | -- | -- 2024-05-01T15:02:26.816464273Z | stdout | 2024-05-01T15:02:26Z INFO Updating record [domain: elmostation.com \| host: @ \| provider: godaddy \| ip: ipv4] to use 42.2.41.218 2024-05-01T15:02:26.816236503Z | stdout | 2024-05-01T15:02:26Z INFO ipv4 address of elmostation.com is 112.118.68.250 and your ipv4 address  is 42.2.41.218 2024-05-01T15:02:26.457594503Z | stdout | 2024-05-01T15:02:26Z INFO [http server] listening on :8000 2024-05-01T15:02:26.457453936Z | stdout | 2024-05-01T15:02:26Z INFO [backup] disabled 2024-05-01T15:02:26.456761051Z | stdout | 2024-05-01T15:02:26Z INFO [healthcheck server] listening on 127.0.0.1:9999 2024-05-01T15:02:26.456350062Z | stdout | 2024-05-01T15:02:26Z INFO Reading history from database: domain elmostation.com host @ ipv4 2024-05-01T15:02:26.277442332Z | stdout | 2024-05-01T15:02:26Z INFO Found single setting to update record 2024-05-01T15:02:26.277368767Z | stdout | 2024-05-01T15:02:26Z INFO reading JSON config from environment variable CONFIG ``` Configuration file (**remove your credentials!**): lastest ```json {"settings":[{"provider":"godaddy","domain":"elmostation.com","host":"@","key":"key","secret":"secret","ip_version":"ipv4","ipv6_suffix":""}]} ``` Host OS: docker
saavagebueno added the Priority: 💤 Low priorityCategory: Config problem 📝 labels 2025-11-20 04:23:30 -05:00
saavagebueno commented 2025-11-20 04:23:30 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (May 1, 2024):

Check your key and secret have the permission to edit the dns record for that domain

403: Authenticated user is not allowed access os the error message coming from Godaddy directly, highlighting you authenticated correctly (so unlikely a ddns-updater bug), but it has not the permission to do the change.

@qdm12 commented on GitHub (May 1, 2024): Check your key and secret have the permission to edit the dns record for that domain `403: Authenticated user is not allowed access` os the error message coming from Godaddy directly, highlighting you authenticated correctly (so unlikely a ddns-updater bug), but it has not the permission to do the change.
saavagebueno commented 2025-11-20 04:23:31 -05:00
Author
Owner
Copy Link

@ChristianChoi commented on GitHub (May 1, 2024):

FYI, I'm experiencing the same issue while tring to add a new host/subdomain to my existing godaddy configuration that used to work.
I have also tried creating a new API key+secret in GoDaddy, but still getting the same error.
Also, I don't see anywhere in GoDaddy's developer portal where permissions can be modified for an API key.

Edit: I googled to see if anyone else are having issues with the GoDaddy API recently and stumbled upon this https://publish.reddit.com/embed?url=https://www.reddit.com/r/godaddy/comments/1bl0f5r/comment/kyxjua5/

"We wanted to inform you that we have recently updated our Domain API requirements. As part of this update, customers are now required to have 20 or more domains in their account to utilize the API.
However, we want to assure you that you still have access to the OTE API without any blocks."

Guess it's time to migrate to Cloudflare...

@ChristianChoi commented on GitHub (May 1, 2024): FYI, I'm experiencing the same issue while tring to add a new host/subdomain to my existing godaddy configuration that used to work. I have also tried creating a new API key+secret in GoDaddy, but still getting the same error. Also, I don't see anywhere in GoDaddy's developer portal where permissions can be modified for an API key. Edit: I googled to see if anyone else are having issues with the GoDaddy API recently and stumbled upon this https://publish.reddit.com/embed?url=https://www.reddit.com/r/godaddy/comments/1bl0f5r/comment/kyxjua5/ > "We wanted to inform you that we have recently updated our Domain API requirements. As part of this update, customers are now required to have 20 or more domains in their account to utilize the API. > However, we want to assure you that you still have access to the OTE API without any blocks." Guess it's time to migrate to Cloudflare...
saavagebueno commented 2025-11-20 04:23:31 -05:00
Author
Owner
Copy Link

@teopost commented on GitHub (May 2, 2024):

Starting from May 1st, I'm getting the same error.
I sent an email to support and they replied with this:

Hi,

We have recently updated the account requirements to access parts of our production Domains API. 
As part of this update, access to these APIs are now limited:

Availability API: Limited to accounts with 50 or more domains
Management and DNS APIs: Limited to accounts with 10 or more domains 
and/or an active Discount Domain Club plan.
If you have lost access to these APIs, but feel you meet these requirements, 
please reply back with your account number and we will review your account 
and whitelist you if we have denied you access in error.

Please note that this does not affect your access to any of our OTE APIs.

If you have any further questions or need assistance with other API questions, 
please reach out.

Regards,

API Support Team
@teopost commented on GitHub (May 2, 2024): Starting from May 1st, I'm getting the same error. I sent an email to support and they replied with this: ``` Hi, We have recently updated the account requirements to access parts of our production Domains API. As part of this update, access to these APIs are now limited: Availability API: Limited to accounts with 50 or more domains Management and DNS APIs: Limited to accounts with 10 or more domains and/or an active Discount Domain Club plan. If you have lost access to these APIs, but feel you meet these requirements, please reply back with your account number and we will review your account and whitelist you if we have denied you access in error. Please note that this does not affect your access to any of our OTE APIs. If you have any further questions or need assistance with other API questions, please reach out. Regards, API Support Team ```
saavagebueno commented 2025-11-20 04:23:31 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (May 2, 2024):

Oh that sucks. Let me codify this in case a 403 status is received.

@qdm12 commented on GitHub (May 2, 2024): Oh that sucks. Let me codify this in case a 403 status is received.
saavagebueno commented 2025-11-20 04:23:31 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (May 2, 2024):

Thanks @teopost your comment is linked in the code from commit d3541da812

If you get a 403 status with that particular error message, it's now logging to check your comment. Closing this as resolved.

@qdm12 commented on GitHub (May 2, 2024): Thanks @teopost your comment is linked in the code from commit d3541da8124970897e3c17c744207156663a79a6 If you get a 403 status with that particular error message, it's now logging to check your comment. Closing this as resolved.
saavagebueno commented 2025-11-20 04:23:31 -05:00
Author
Owner
Copy Link

@kayaozalp commented on GitHub (May 4, 2024):

Just seen this error pop-up after an IP change. Spent an half an hour on the phone with customer support, most of it trying to explain what an API is, to finally being told to email api@godaddy.com
I suspect I will receive the exact same message as above.
Quoting from my email to them: "Making this change, for a paid in advance service, I find it unethical, and making the change unannounced to the users impacted is unprofessional."

I do not expect anything to come-out from this, besides moving to a different domain provider.

@kayaozalp commented on GitHub (May 4, 2024): Just seen this error pop-up after an IP change. Spent an half an hour on the phone with customer support, most of it trying to explain what an API is, to finally being told to email api@godaddy.com I suspect I will receive the exact same message as above. Quoting from my email to them: "Making this change, for a paid in advance service, I find it unethical, and making the change unannounced to the users impacted is unprofessional." I do not expect anything to come-out from this, besides moving to a different domain provider.
saavagebueno commented 2025-11-20 04:23:31 -05:00
Author
Owner
Copy Link

@gr33k commented on GitHub (May 13, 2024):

I'll refrain from making rude comments regarding godaddy...but this is quite unfortunate. With this in effect, does this make this tool 'useless' unless you have their minimum required domains (I assume that is the sad case)?

EDIT: Useless for GoDaddy specifically (as that is what I use but don't have 10 domains with them)

@gr33k commented on GitHub (May 13, 2024): I'll refrain from making rude comments regarding godaddy...but this is quite unfortunate. With this in effect, does this make this tool 'useless' unless you have their minimum required domains (I assume that is the sad case)? EDIT: Useless for GoDaddy specifically (as that is what I use but don't have 10 domains with them)
saavagebueno commented 2025-11-20 04:23:32 -05:00
Author
Owner
Copy Link

@ChristianChoi commented on GitHub (May 13, 2024):

This tool is not useless at all, but GoDaddy is useless. Personally, I switched to Cloudflare DNS within 5minutes, and I suggest you do the same (or any other DNS service than GoDaddy)

@ChristianChoi commented on GitHub (May 13, 2024): This tool is not useless at all, but GoDaddy is useless. Personally, I switched to Cloudflare DNS within 5minutes, and I suggest you do the same (or any other DNS service than GoDaddy)
saavagebueno commented 2025-11-20 04:23:32 -05:00
Author
Owner
Copy Link

@BH1SCW commented on GitHub (Nov 30, 2024):

I also switched to Cloudflare, everything works well now, shit GoDaddy

@BH1SCW commented on GitHub (Nov 30, 2024): I also switched to Cloudflare, everything works well now, shit GoDaddy
saavagebueno commented 2025-11-20 04:23:32 -05:00
Author
Owner
Copy Link

@SquadCraftFTW commented on GitHub (Jul 25, 2025):

I just got this domain today so I have to wait before switching :/

@SquadCraftFTW commented on GitHub (Jul 25, 2025): I just got this domain today so I have to wait before switching :/
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Category: Config problem 📝
Category: Database 🗃️
Category: Documentation ✒️
Category: Foolproof settings 👼
Category: Good idea 🎯
Category: Healthcheck 🩺
Category: IP fetching 📥
Category: Label missing ❗
Category: Maintenance ⛓️
Category: Motivated! 🙌
Category: New provider 🆕
Category: Provider update ♻️
Category: Shoutrrr 📢
Category: Web UI 🖱️
Category: Wildcard 🃏
Closed: ⚰️ Inactive
Closed: 👥 Duplicate
Closed: 🗑️ Bad issue
Complexity: ☣️ Hard to do
Complexity: 🟩 Easy to do
Priority: 💤 Low priority
Priority: 🚨 Urgent
pull-request
Mirrored from GitHub Pull Request
 Status: 🔒 After next release
Status: 🔴 Blocked
Status: 🗯️ Waiting for feedback
No Label Category: Config problem 📝 Priority: 💤 Low priority
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#392
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?