#I don't know. how can i make shure it's
digital kite
Did you set anything up? Sign up for the NabuCasa #cloud-archived service? Configure DuckDNS + SSL? Anything?
Because if you didn't do anything then you don't have remote access
And as the GA docs tell you, you need that
devout reef
Did you set anything up? Sign up for the NabuCasa <#402899129660997642> service?...
are clouds paid?
digital kite
The Nabu Casa service is
DuckDNS is free
The cloud service also has UI point-n-click setup for Google Assistant 😛
devout reef
Manual setup (if you don’t have Home Assistant Cloud)
devout reef
I don't have any cloud service.
digital kite
Then you have to set up remote access manually
DuckDNS is the way a lot of people go, but there's many options
devout reef
DuckDNS is free
what are the "-"
devout reef
the downsides of that cloud
digital kite
Well, Nabu Casa is easy and paid for
DuckDNS, and the other options, are free and work from you
digital kite
- install the DuckDNS add-on
- Read the docs for it
- Read the link above
devout reef
- done
digital kite
Now read the docs for it
Then, once you understand how to set it up, read the forum link above which covers all the things you need for port forwarding, and more
digital kite
pick-whatever-you-want.duckdns.org
digital kite
Did you tell it to get you SSL certs from LetsEncrypt?
Or did you skip past that part of the docs?
devout reef
Did you tell it to get you SSL certs from LetsEncrypt?
e?
digital kite
The docs... you really should read the docs
They tell you how to get SSL certs
These settings only apply to Let's Encrypt SSL certificates
You want those
You need SSL
digital kite
No
toxic zealotBOT
digital kite
You need the docs that come with the add-on
I don't use add-ons, so all I can tell you is that they exist
digital kite
Says addons in the URL... looks good 😉
digital kite
Then config check, then restart HA
At that point you must always use https:// to access HA
When using anything other than the hostname in the cert you'll get errors, because that's how SSL works
devout reef
At that point you ***must always*** use `https://` to access HA
HA means home assistant? right?
digital kite
Yes
devout reef
accept_terms: true
certfile: fullchain.pem
keyfile: privkey.pem
token: sdfj-2131023-dslfjsd-12321
domains:
- my-domain.duckdns.org
aliases: []
seconds: 300```can i set this in the addon configuration and don't put it in to config....ymlnah
from docs
yh but there is also this config tabhttps://imgur.com/a/jlNtPrf
so should i use config tab or config file?
digital kite
The add-on config tab is for the add-on config, to save you editing files
They just format it differently
devout reef
```http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem```
what to do with this?
digital kite
#add-ons-archived can help you, but the obvious answer is to paste the relevant parts into the right bits of the add-on UI
frosty sparrow
You enter that in configuration.yaml
devout reef
At that point you ***must always*** use `https://` to access HA
and my url that does not have eaven http:// just http://homeassistant.local:8123
digital kite
Ah, that bit, yeah... I've got lost 
devout reef
You enter that in configuration.yaml
i don't have thease variables
digital kite
and my url that does not have eaven http:// just http://homeassistant.local:8123
And it will now have to use https://
Because once you set HA up for SSL, it's 100% SSL 100% of the time
toxic zealotBOT
digital kite
Yes, that
devout reef
fuck this mention feture set on defult
This site can’t provide a secure connection
homeassistant.local sent an invalid response.
digital kite
Once you've added those lines to configuration.yaml, run your config check, and restarted HA, you can't use http:// any more
Because you haven't yet finished
devout reef
oh
devout reef
```http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem```
thease?
digital kite
Still yes
frosty sparrow
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
That goes in configuration.yaml
I don't know what variables you are talking about
devout reef
i don't have thease variables
^
devout reef
something have to be in /ssl/privkey.pem ?
frosty sparrow
Yes, DuckDNS add-on puts those files there
When you run it and check the add-on logs you'll see this
digital kite
And the add-on only puts them there once you've set it up correctly
Step #1 remains getting that done
I suspect you're still working on that... given what you posted above
You need to slow down, and do things in order, or you're just going to continue to struggle
devout reef
This site can’t be reached
homeassistant.local refused to connect.
something is not right
digital kite
HA should still start up, but with http:// to access it
frosty sparrow
if you added this incorrectly, it would use http: to access. If you added it correctly, you would use https:// and you would see a warning
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
devout reef
I'm so sorry
devout reef
HA should still start up, but with `http://` to access it
It did
In recovery mode
Here's the error log
devout reef
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
i did delete this and it booted up
frosty sparrow
So next you try entering it correctly
And check config or show what you have entered before restarting
devout reef
i ha core checked
but i can't crtl+shift+c becuse of some keybind in my browser
is it okay if i sent i picture?
frosty sparrow
You can link to one yes
devout reef
frosty sparrow
A screenshot of what you have entered would be better
devout reef
intro config file?
frosty sparrow
That’s where it’s going wrong
devout reef
# Loads default set of integrations. Do not remove.
default_config:
# Load frontend themes from the themes folder
frontend:
themes: !include_dir_merge_named themes
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
# Example configuration.yaml entry
google_assistant:
project_id: home-asistant-44364
service_account: !include SERVICE_ACCOUNT.JSON
report_state: true
expose_by_default: false
entity_config:
switch.kitchen:
name: "light"
expose: true
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
Oh is the add on running?
devout reef
witch one?
frosty sparrow
Duckdns
devout reef
yh
frosty sparrow
what do the add on logs show
devout reef
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
digital kite
Then troubleshooting needs to wait until you're home
devout reef
back home
and it is back online
# INFO: Using main config file /data/workdir/config
+ Creating chain cache directory /data/workdir/chains
Processing radareek.duckdns.org
+ Creating new directory /data/letsencrypt/radareek.duckdns.org ...
+ Signing domains...
+ Generating private key...
+ Generating signing request...
+ Requesting new certificate order from CA...
+ Received 1 authorizations URLs from the CA
+ Handling authorization for radareek.duckdns.org
+ 1 pending challenge(s)
+ Deploying challenge tokens...
OK + Responding to challenge for radareek.duckdns.org authorization...
+ Challenge is valid!
+ Cleaning challenge tokens...
OK + Requesting certificate...
+ Checking certificate...
+ Done!
+ Creating fullchain.pem...
+ Done!13:26:44] INFO: Renew certificate for domains: radareek.duckdns.org and aliases:
# INFO: Using main config file /data/workdir/config
+ Creating chain cache directory /data/workdir/chains
Processing radareek.duckdns.org
+ Creating new directory /data/letsencrypt/radareek.duckdns.org ...
+ Signing domains...
+ Generating private key...
+ Generating signing request...
+ Requesting new certificate order from CA...
+ Received 1 authorizations URLs from the CA
+ Handling authorization for radareek.duckdns.org
+ 1 pending challenge(s)
+ Deploying challenge tokens...
OK + Responding to challenge for radareek.duckdns.org authorization...
+ Challenge is valid!
+ Cleaning challenge tokens...
OK + Requesting certificate...
+ Checking certificate...
+ Done!
+ Creating fullchain.pem...
+ Done!```log looks good
but it's still in http
proly becuse i don't have that script in my config file
now i lost it
idk what's wrong
i can't see the server in my app
digital kite
What did you change?
digital kite
That's the lets encrypt terms 😉
None of that would cause you to lose access to HA itself though
devout reef
and than added this to config:
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
and restarted
after the restart i cano't acces it
digital kite
Did you remember to use https:// now?
digital kite
Not unless you've set up port forwarding already
devout reef
Is `yh` a _yes_ or a _no_ or a ...?
yeah
digital kite
And did you try with just http://?
digital kite
Now "all" you have to do is sort out port forwarding so you can connect remotely
Then you can get back to sorting out the Google Assistant integration
devout reef
but i don't have a certificate, so the app doesn't let me put it in
digital kite
You're using https:// ...
Without a certificate you can't 😉
So ... yes, you have one
The HA app will also only connect to the hostname in the certificate, your DuckDNS hostname
devout reef
digital kite
Yes ... you have a cert
devout reef
digital kite
Right...
devout reef
it says cert is not valid
digital kite
We've covered that before
Let me find the link to save me writing it all out again, and again 😉
digital kite
No
digital kite
Now "all" you have to do is sort out port forwarding so you can connect remotely
That second one has the guide you need
digital kite
All of that guide, but yes
digital kite
Did you actually forward any yet?
devout reef
i don't know
digital kite
FFS
You have to follow the guide step by step, if you're jumping around at random then you're doomed
And you really should know if you've forwarded a port... if you've not opened up your router's admin pages then no, you haven't
If this is all proving too much for you, paying for the Nabu Casa cloud service will be easier 😛
digital kite
Then you get to pay attention and go step by step
devout reef
ok
digital kite
Or you can keep chasing squirrels...
devout reef
is Port forwarding safe?
digital kite
Yes/no/maybe
In itself, security neutral
The question is.... have you secured the thing you're forwarding to?
And that's covered in the guide
devout reef
The question is.... have you secured the thing you're forwarding _to_?
what thing?
digital kite
Home Assistant... what else?