Thank you so much for building this add-on and for responding to my post. I am up and running.
Where is the “DNS add-on configuration” in Godaddy?
I see DNS Management which has Records and Nameservers and then under Advanced Features I have the option to add Premium DNS.
Am I looking in the right section?
Major noob here.
The add-on configuration is in Home Assistant, not on GoDaddy’s website.
- Navigate in your Home Assistant front-end to “Supervisor”
- In the list of installed add-ons, you should have “GoDaddy DNS”. Click on it.
- At the top (or bottom) of the GoDaddy DNS add-on page, there will be a “Configuration” section. Click on it.
- Change the configuration text and then click on “Save”.
I think HA will prompt you to restart the add-on if you make changes, which you should do.
Thanks Michael. I won’t be quitting my day job any time soon.
Ok so GoDaddy DNS is up and running and everything seems to be ok in the log saying “Renewal successful for domain: <subdomain.my_domain>.com”
However I can’t access HA using .<my_domain>.com and the address ip:8123 is still not secure.
I’ve added the below in the configuration text file. (Assuming this is configuration.yaml)
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
Am I missing something here?
Do I need to make any changes with regard to Forwarding within GoDaddy?
From what you’ve said, I think you’re probably done with the GoDaddy website and configuring the GoDaddy DNS add-on in HA.
Did you restart HA after adding the http section to configuration.yaml?
If you try to connect like this (pretending 192.168.0.8 is your HA’s private IP address):
http://192.168.0.8:8123/
You should get some type of error about making an HTTP request to an HTTPS port.
If you try to connect like this (notice the s):
https://192.168.0.8:8123/
You should get a warning from your browser that the certificate cannot be validated and your connection may not be secure private. Usually, you can bypass this warning (by clicking “Advanced” and then proceeding or continuing).
The only way to connect without errors or warnings will now be through your host name (assuming my-hostname.my-godaddy-domain.com is your domain name and 12345 is the port you’ve randomly chosen to forward on your router):
https://my-hostname.my-godaddy-domain.com:12345/
Ok good to know.
I’ve had to re-input the below code using File editor.
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
However I can only access HA by going to https://ip.8123 and clicking Advanced.
When I try to access HA using https://my-hostname.my-godaddy-domain.com I get taken to the below screenshot.
I haven’t chosen a port to forward on my router because I don’t know where and how this step is done?
That screenshot looks like a login for your “TP-Link” router, which is allowing connections on HTTPS port 443 of your public IP address… Not something that I personally would want to see (not great security in my opinion), but maybe it’s only allowing it because you’re accessing it from your internal network…
Setting up port forwarding is a bit outside the scope of this thread. Every router is different, but in most cases you can do it by navigating your web browser to the router’s internal IP address, logging on, and then entering the forwarding settings into its web interface.
I’ve already explained earlier in this thread how to do the port forwarding, but you’ll have to figure out what model of router you have and how to configure it. You can probably download a manual for it from the manufacturer’s website. If it isn’t still set to a default username and password listed in the manual, then you might need to contact your ISP to get those. Or maybe they might be listed on a sticker on your router?
Just a bit of advice… Since the router already appears to be answering on external port 443, you’ll probably have to pick a different external port number to avoid a conflict. You could just use 8123 to keep things simple:
- external/service port 8123 → 192.168.0.8:8123
(again, pretending 192.168.0.8 is your HA’s private IP address)
Because it isn’t the default 443, you’ll have to include the port number when connecting to your HA:
https://my-hostname.my-godaddy-domain.com:8123/
1 Like
Hi Michael,
I raised the issue in Github, but then found this thread and thought it could be actually better place to ask for help.
Will be appreciated if you could have a look on the error.
Cheers,
Alex.
This is a known problem with running HA on some custom docker hosts (basically anything other than the Home Assistant Operating System) and installing add-ons which require OpenSSL. To fix, update libseccomp2 on the host.
See this thread for more information:
Thanks Michael!
The problem is I do run Home Assistant Operating System in a full blown VM on ESXi host. So I guess issue above is not really my case? I commented in the thread you mentioned and Chris seems agreed.
Still can’t install the plugin and will be appreciated for any ideas.
Regards,
Alex.
I am loving this addon, Thank you very much! Have it working perfectly for my GD subdomain. I also run Vaultwarden addon with a separate subdomain. Is there anyway to provide DNS updates to multiple subdomains?
Again, thank you!
So how does this addon actually work? Does it detect a WAN-ip change and then calls to GoDaddy?
I’ve installed it, but the logs don’t give much info about the update process working or not.
(I’m not using Let’s Encrypt)
Thank you so much for this Add-On! Its working beautifully and was super easy to setup. Cheers! 
Works beautifully, thank you so much for that!
I’ve been using this successfully with two hosts.
However I added a new home assistant host today, and there seems to be an issue with Godaddy API. I get the following error when looking in the log. I also have starting getting this on the older hosts, which have been working as they should for the past year.
Attatched is the error:
- Deploying challenge tokens…
{“code”:“ACCESS_DENIED”,“message”:“Authenticated user is not allowed access”}
Seems like the issue is with Godaddy…
Yep, they have introduced restrictions to the API usage, you need to have at least 10 domains to be able to use the API or a paid subscription. Introduced without any warning or communication to customers. Still there is not a single word about those restrictions. I’ve spent almost an hour on a phone with their support and they were not able to tell me what’s wrong. I’ve transferred my domain to name.com - their API works all OK.
Are you using some other addon to update the dns at name.com? Please share your process, I’ll be forced to switch as well.
No addons. I have a shell script running on my NAS (TrueNAS) that is updating the DNS record pointing to my server. This is based on those instructions, now obviously updated to the name.com API. https://www.instructables.com/Quick-and-Dirty-Dynamic-DNS-Using-GoDaddy/
Also some other scripts (using the acme.sh certificate automatic renewal) automatically renewing letscencrypt certificate and deploying it all over the place to various services (e.g. nginx reverse proxy, plex, truenas, portainer etc.).
I have kept my domain name with godaddy, due to I’m using personalized email with Outlook.com. Microsoft\Outlook.com Office 365 family only supports GoDaddy as domain name provider with the use of personalized email. So the new api poll limitation from GoDaddy was a huge downside for me.
However I managed to keep GoDaddy and the personalized email. But I have pointed the GoDaddy domain registrars to use Cloudflare DNS servers and copied the domain zone file(DNS registers) from GoDaddy to Cloudflare. Then I get the best from both worlds with keeping personalized email with Office 365 Family and using Cloudflare DNS servers (using the official HA - Let’s Encrypt addon to generate new certificates from Cloudflare).
1 Like