-
Notifications
You must be signed in to change notification settings - Fork 16
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
Still in DEV? #19
Comments
Not sure if Im having the same issue or at least similar, noticed today the dns hadnt updated the the logs show: {"code":"ACCESS_DENIED","message":"Authenticated user is not allowed access"} Been working fine for years nothing changed. Tried generating a new key and secret and get the same error message |
I understand that this is a new block by GoDaddy. Nothing we can do about it. |
as in Go Daddy are blocking API access anyone got any experience requesting it to be unblocked? |
https://www.reddit.com/r/godaddy/comments/1bl0f5r/am_i_the_only_one_who_cant_use_the_api/ suggests they are giving different answers but effectively you need at least 10 domains before your account can use the dns api, time to find a new host |
Same experience here...certification expiration and no chance to renew it (error access denied...) |
I left my domain at go-daddy but moved the dns to cloudflare for free and then use the cloudflare integration to update dns. When my domain renews Ill move it to cloudflare completely |
Issue Resolved with a Different Approach I’ve solved the remote access issue for Home Assistant with an alternative method. Solution: Set up an SSH reverse tunnel to a Digital Ocean droplet with a fixed IP address, using it as a proxy for traffic on port 8123. Benefits: Simple Configuration: The setup process is straightforward (there is also an add on to install autossh) Additionally, I am considering switching from GoDaddy as my domain registrar due to their unacceptable behavior. |
Is the godaddy dns addon still in dev (will it ever be updated) because it seems like it no longer works. I have successfully use it in past and recently came back to it because nginx proxy (w/ letsencrypt) no longer works with godaddy. I am receiving api error. The key&secret are entered in addon config, I dont recall having to enter them in secrets file or creating acme challenge txt file for this addon. I am ust missing something or does this have the same issues as nginx proxy / godaddy?
{"code":"UNABLE_TO_AUTHENTICATE","message":"Unauthorized : Could not authenticate API key/secret"}
The text was updated successfully, but these errors were encountered: