Lets Encrypt - Problem connecting to server (get for https://acme-v01.api.letsencrypt.org/directory; curl returned with 6)

Installation Home Assistant OS
5

If I do this:

Create this file with the following contents to set two DNS, firstly your network’s DNS server, and secondly the Google DNS server to fall back to in case that server isn’t available:

/etc/docker/daemon.json:

{
“dns”: [“192.168.0.1”, “8.8.8.8”]
}
Then restart the docker service:

sudo service docker restart

Then, the DuckDNS addon starts and Letsencrytp is accessed properly, but the other addons break.

P.S.: I am running Hassio in a Ubuntu host.

1 Like
6

Your problems generating new certificates are likely related to this:

For anyone else using unRaid (or Docker for the linuxserver/letsencrypt container) you might also want to read this:

https://lime-technology.com/forums/topic/51808-support-linuxserverio-letsencrypt-nginx/?page=48&tab=comments#comment-619392

7

Hi

Thanks for your post, this validates my understanding of the reason for the issues experienced. There is a need for the developers of the DuckDns Addon to review the issue and adjust the code.

I have raised an issue will link to this post.

8

temporary fix?

9

I use the same settings. Dod you solve?

10

No.
I am afraid that we have to wait for the DuckDNS addon developers to provide a fix or switch to another solution for SSL.
I am considering Caddy if the solution takes long time. But I am a newbie in this issues…

11

try this

1 Like
12

Aaaah! That´s it! I got it finally working.
Thanks a lot!

13

This worked for me also or a coincidence that the ability to ping xxxxxx.duckdns.org started to work?

14

OMG! I love you! I’ve been fighting this issue for a couple days now for this add-on and Custom Dependencies! THANK YOU THANK YOU THANK YOU!

15

This may be already on here but this worked for me with ubuntu 18.04:

sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

solved my issues with duckdns.org and hass.io

7 Likes
16

Hey, thanks for posting your solution after all this time.

It just so happens that I’m also trying to setup duckdns with let’sencrypt and failing miserably. In my case your solution achieved nothing cause I dont have a /run/systemd/resolve/resolv.conf to symlink to so it just creates an empty resolv.conf in /etc/

The other solutions I gathered from other similar threads also fail:

  • creating daemon.json with dns addresses in docker broke hassio
  • mapping port 80 to 85 in my router and then trying to run the addon container with -p 85:80 (I just don’t know the init commands to that.)

My installation is hass.io on a Ubuntu 18.04 server running as a virtualbox VM in windows10. I’ve got no other issues regarding networking and even have Pi-Hole up and running.

Any other ideas would be very welcome and promptly tested

17

Thank you @Eszyman, that fixed my connectivity issues with Hassio and DuckDNS running on Ubuntu Server 17.10, which I have running in VirtualBox within Windows 10.

18

I have been looking for a solution to this problem ever sens I have upgraded my install from 16.04 to 18.04. Your solution is the first one that worked for me. Thank you for you help.

19

I run the " sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf " on my ubuntu 18.04.01, and now i can´t acess to the home assistant page in my home network (192.168.x.x:8123)

20

I have Hassio v. 0.86.3 and I couild’t edir resiolve.cnf file
How can I do to add google dns?

21

Thank you, solved my problem also.
Debian 18.04 and Hass.IO

22

Hello everyone,

I am not having Linux but directly Hassio on my Raspberry 4.
I am having the same issue and I don’t know how to solve it.
I fixed the IP and DNS address using the my_network file and a USB stick but I am not sure of what I should put in the DNS section.
I haven’t configured any port routing yet on my router.

[ipv4]
method=manual
address=192.168.1.17/24;192.168.1.1
dns=192.168.1.1;8.8.8.8;

And here is what I put in configuration.yaml file:

http:
  base_url: !secret my_base_url
  server_port: 8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  ip_ban_enabled: true
  login_attempts_threshold: 3
23

Hi, you have found a solution ? i am having the same problems.

24

Thanks!
The very same solution worked for me in 2024!