I cannot access home assitant. Nor via duckdns, nor via ssh

lordwizzard · February 5, 2023, 4:21am

Creating a secured connection so you can us HTTPS from outside into HA. I think the OP is trying to do it this way: Securing - Home Assistant

Hugues · February 5, 2023, 4:24am

I have installed the add-on duckdns.

lordwizzard · February 5, 2023, 4:25am

So you followed the steps correctly then?

I don’t see any info on the Add-on and what is needed?

Hugues · February 5, 2023, 4:28am

Well, I believe I followed the steps as described. That’s why i do not understand why my configuration.yaml gives me this error message.

lordwizzard · February 5, 2023, 4:30am

Had to google and found the docs on github.

github.com

home-assistant/addons/blob/dc587cd95fd7b87fc7abd87740e08c7b36903ecd/duckdns/DOCS.md

# Home Assistant Add-on: DuckDNS

## Installation

Follow these steps to get the add-on installed on your system:

1. Navigate in your Home Assistant frontend to **Supervisor** -> **Add-on Store**.
2. Find the "DuckDNS" add-on and click it.
3. Click on the "INSTALL" button.

## How to use

1. Visit [DuckDNS.org](https://www.duckdns.org/) and create an account by logging in through any of the available account services (Google, Github, Twitter, Persona, Reddit).
2. In the `Domains` section, type the name of the subdomain you wish to register and click `add domain`.
3. If registration was a success, the subdomain is listed in the `Domains` section along with `current ip` being the public IP address of the device you are currently using to access `duckdns.org`. The IP address will be updated by the DuckDNS add-on.
4. In the DuckDNS add-on configuration, perform the following:
    - Copy the DuckDNS token (listed at the top of the page where account details are displayed) from `duckdns.org` and paste into the `token` option.
    - Update the `domains` option with the full domain name you registered. E.g., `my-domain.duckdns.org`.

## Configuration

This file has been truncated. show original

Hugues · February 5, 2023, 4:35am

i did all this except adding these in configuration.yaml

Example configuration.yaml entry

duckdns:
domain: YOUR_SUBDOMAIN
access_token: YOUR_ACCESS_TOKEN

It was not described anywhere to add thes extra line in the file.

lordwizzard · February 5, 2023, 4:36am

I would try to make sure to follow the github docs. Add what is missing and try again.

Hugues · February 5, 2023, 4:37am

Ok. I will have a look at it. Thanks for helping me.

lordwizzard · February 5, 2023, 4:39am

Also add the next section for http: also because it is needed by the HA.

http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

Hugues · February 5, 2023, 4:45am

This was already added and it was by adding these extra lines that it gave me the error message.

lordwizzard · February 5, 2023, 4:55am

I looked at what you had posted, you had https: on line 24 and in line 25 they should not be like that from the docs.

Hugues · February 5, 2023, 11:13am

What is wrong about lines 24 and 25?

Nick4 · February 5, 2023, 11:38am

Have you checked that the ports are being forwarded?
If not: https://canyouseeme.org
If not forwarded: have you tried rebooting your router?
Does your duckdns domain point to the right address?

aceindy · February 5, 2023, 11:43am

There is not supposed to be an ‘s’
just

http:

EdwardTFN · February 5, 2023, 2:07pm

So, I understand you can access using httpS with the your DuckDNS address (https://your domain.duckdns.org/), is that correct?

If so, then you have all the files you need, so I will suggest to do the following:

Install and start the add-on: NGINX Home Assistant SSL proxy
This add-on will help you managing the different connections thru HTTPS when using your DuckDNS address and HTTP when using http://homeassistant.local:8123.
Note that you need some settings (adding your DuckDNS domain into NGINX settings).
Comment out the files on your http session on configuration.yaml and add a trusted proxy, like this:

http:
  #ssl_certificate: /ssl/fullchain.pem
  #ssl_key: /ssl/privkey.pem
  ip_ban_enabled: false. #change this to true after everything is working properly
  login_attempts_threshold: 5
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.0/24

Make sure you have your router forwarding external port 443 to Home Assistant port 443.
The other ports on your router are not needed after the security key files are created, which I believe they are (you can double check on DuckDNS add-on Logs).
Go to Settings → System → Network and add your two addresses for Home Assistant:

image1204×844 96.7 KB
Restart Home Assistant
Try to access your Home Assistant from both those addresses:
http://homeassistant.local:8123
https://yourdomain.duckdns.org/

Nick4 · February 5, 2023, 3:41pm

No Edward, he could not access it at all at first.
From LAN because he was using unsecured http but with https & the HA IP it works.
Using his duckdns domain does not work.

The point is: did he do something wrong (which is already obvious from adding https to the http configuration) or is he trying from his LAN and the router does not allow NAT loopback.
Another possibility is that the ports are not open/redirected.

EdwardTFN · February 5, 2023, 4:09pm

OK, then this work:

https://homeassistant.local

But none of those are working:

Is that correct?

If that is the case, the first step is to double check if the certificate files has being create (otherwise not even NGINX would help).
In order to check for the cert files, take a look on the DuckDNS logs:

odwide · February 5, 2023, 4:52pm

Newer versions of Android won’t connect to .local domains, the same for iOS.

Edit: .local is now strictly handled by Android for mDNS purposes and not for unicast address resolution. Recommendation is to stay away from .local domains.

https://source.android.com/docs/core/ota/modular-system/dns-resolver#mdns-local-resolution