Error:
jq: error (at <stdin>:0): Cannot iterate over null (null)
I am also interested in leveraging the Bitwarden add-in. Will this add-in support SSL for both Hassio AND additional add-ins one might add? Figured I would post here to check before I jump into the code…
First off, thanks for the add-on @hars.
I just came back to my hassio install after some time to find that letsdnsocloud is erroring out complaining about nonces. It looks like the Dehydrated version needs to be bumped based on these bug threads: https://github.com/lukas2511/dehydrated/issues/684
https://community.letsencrypt.org/t/jws-has-no-anti-replay-nonce/103324/16
It seems that forcing a rebuild/rerunning the add-on repeatedly got it to randomly work (which reports on those threads suggested would work as well) but getting upstream Dehydrated fixes to get around this properly probably aren’t a bad idea.
already running the latest release: https://github.com/PhrantiK/hassio-addons/blob/36e9f0e5ecc633b008654ee6cea1383d45bc2dd6/letsdnsocloud/build.json
What is the exact error message you’re getting?
I haven’t touched my Hassio install in months as it “just works”. If I find the time I’ll update and see if I get the error messages.
I’m not 100% certain but I think you’ll need a reverse proxy for multiple services.
Thanks for creating this addon, looks like a perfect fit for my use case.
I’m having an issue though while following the instructions. After starting the addon, I get the following error message (same as @bakes82 above):
jq: error (at <stdin>:0): Cannot iterate over null (null)
And then the addon stops. No changes to my DNS records or generated SSL certificates.
Is anyone able to help?
Running the latest Hass.io / Home Assistant on a Raspberry Pi 3B+.
Finally had the time to update my hassos and hass.io to the latest version, I deleted my certs & add-on and started from scratch.
Everything went smooth with no errors.
The only thing I can think of is you have an error in your config. There’s three sections you need to change, check out the below. Just replace the **** with your options and make sure there’s no spaces etc.
{
"lets_encrypt": {
"accept_terms": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"cfapikey": "****",
"cfemail": "****",
"domains": [
"****"
],
"seconds": 300
}
Thanks for looking into it. I got it working now after carefully going over the guide and double-checking everything.
The problem was that I had generated and used an API Token. After I replaced it with the global API key, everything has been working well!
Thanks again for this awesome extensions! 
1 Like
First off, thanks for this add-on! I think I’m most of the way there in getting it to work. I installed the add-on, set the config variables, added to configuration.yml, and restarted. I am able to access the login-in page on my subdomain (hassio.example.app), but when I enter my credentials and log in, the page hangs at “Loading data.”
Have you experienced this before?
Also worth noting, I am still able to log in locally at https://localhost:8123, it’s just the remote login that hangs at that “Loading data” step.
My setup is: fresh hassio in Docker install (0.103.3), .app domain with Google Domains, Cloudflare set up as DNS for the domain (with SSL option set to “Full (strict)”), port forwarding 443 → 8123.
Thought it may have had something to do with the strict SSL as I had those features turned off in cloudflare.
Just went through and set it to strict and also perform http to https redirects and everything seems to work ok.
I would try turning the cloud flare features off though to eliminate. Provided you’re only forwarding 443 regular http traffic won’t work anyway so it’s safe to turn off.
Also try turning DNS proxy off if you have it set to on.
Thanks for the reply. It turns out it was because AT&T fiber modem+routers don’t support NAT loopback, so it appeared to not be working when I was on my home network. Discovered this when I tried logging in to my custom subdomain from my cell phone and everything was good. So “Full (strict)” SSL does seem to work fine.
Hi. Love the idea of this but get an error when starting the addon:
ERROR: This script requires an openssl binary.
I am running hass.io om Ubuntu docker.
Anyone?
Just merged the fix - wasn’t getting notifications from git, apologies for the delay.
Hi, does this add-on still work? I’m running HA 107.7 and can’t seem to run it. I forwarded the nameservers of my own domains to Cloudflare and it’s active there. Filled in the required info in the addon settings and hit run. The log shows this:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[cmd] /run.sh exited 3
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
After I reload the page the add-on isn’t running and I can’t access it using my own domain.
I still have DuckDNS setup btw. I’m trying to activate your DNS solution before I turn of DuckDNS completely (want to prevent that I remove that and yours doesn’t work).
Any ideas?
Works like a charm, configured it on a subdomain. Elegant and straightforward. Thank you @hars !
1 Like
There’s a lot of shared code between the two addons. I used their method for issuing the certs so it’s likely a conflict.
I removed the certs in the ssl/ folder, restarted HA and ran your add-on again. Gives the same output and there are no certs created in ssl/ folder.
Any idead?
I don’t know how it is possible that this add-on is not super-popular! It’s great, and now I can finally have a beautiful url that feels “home”. Thank you very much!
2 Likes
What are you running hassio on? A raspberry pi or some other hardware?
Does the duckdns add-on work ok?