Home assistant with Raspbian stretch + Docker + DuckDNS

Installation
1

Good Morning everyone,

i’m rather new to home assistant and their community. So if there is something I’ve missed or still don’t know just tell me.

I’m trying to configure my home assistant on a raspberry pi Model 3b+ with Raspbian Stretch Lite and Docker to be accessable from the internet.

My docker-compose file looks like:

version: '3'
services:
  homeassistant:
    container_name: home-assistant
	image: homeassistant/raspberrypi3-homeassistant:latest
	volumes:
	  - /home-assistant:/config
	  - /etc/localtime:/etc/localtime:ro
	restart: always
	environment:
	  - TZ=Europe/Berlin
	ports:
	  - "8123:8123"

I’ve followed the installation instructions on duckDNS

Pi_1
Pi_11401×161 9.02 KB

and also forwarded the following ports for both TCP / UDP:

  • 80 external to 80 internal
  • 8123 external to 8123 internal

The IP adress shown on the duckdns page matches my external ip adress.

I know that this way won’t be secure but i first want my pi to be accessable and than move on to secure it with SSL…

Can someone tell what I’m doing wrong?

Thanks in advance :slight_smile:

2

I guess we should start with, what problem are you having?

3

The only way i can acces home assistent is with the pis ip:8123.

And I can not access http://mydomain.duckdns.org

4

Ok. Did you adjust your config yaml for duckdns? Set the base URL?

5

I followed the instructiona from here:

and added the duckdns section to my configuration.yml

I have not changed the base url…

6

The duckdns component is just to keep your IP updated with duckdns. It doesn’t do anything for actual remote use.

You need to set a base URL as explained in the http component

7

Okay i’ve added the base_url entry to my configuration.yml file restarted home assistant but still http://mydomain.duckdns.org is not accessable.

 http:
   base_url: http://mydomain.duckdns.org:8123

 duckdns:
   domain: domain_name
   access_token: token

Chrome says: Website not reachable.
ERR_CONNECTION_TIMED_OUT

8

Remove http://

9

No changes - still not accessable :confused:

10

Are you sure you’re not behind a carrier grade NAT?

Does your wan IP on your router match when you go to ipchicken.com?

Does your router support hairpin NAT? Are you testing from outside your network or inside?

11

The IP of my router matches the one shown at ipchicken.com
After some research it turns out that it’s not possible to access the dns domain from inside the network.

I’ve tested with my smartphone and i can successfully connect to my home assistant instance via dns and my public ip.

Thank you verry much for pointing me into the right direction :+1:

12

Have a look at running DNSMasq to force your internal network to resolve your DuckDNS name to a local IP