#Problems setting up NGINX for HA

1 messages · Page 1 of 1 (latest)

stoic estuary
#

Safe depends on whether you did all that correctly, and have sensible passwords for all the HA accounts

#

if you created an account called admin with the password admin ... well, not very safe

mellow tinsel
#

no my user is diferent, and password I think is safe..letters, cap letters, numbers..

mellow tinsel
#
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  
http:  
  use_x_forwarded_for: true
  trusted_proxies: 172.30.0.0/16```
thorn locustBOT
#

To format your text as code, enter three backticks on the first line, press Enter for a new line, paste your code, press Enter again for another new line, and lastly three more backticks.
```yaml
example: here
```
Don't forget you can edit your post rather than repeatedly posting the same thing.

stoic estuary
#

You can only have http: once

mellow tinsel
thorn locustBOT
stoic estuary
#

Well, also... what are you doing?

mellow tinsel
#

I have this error in configuration.yaml but aparently work without problems

stoic estuary
#

You've got two lines fo SSL in HA

#

You've got two lines for a reverse proxy

mellow tinsel
#

I use duckDNS and the NGinx

stoic estuary
#

Then remove the ssl_ lines

mellow tinsel
#

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

stoic estuary
#

Yes

mellow tinsel
#

If I remove that the remote access doesnt work..

stoic estuary
#

Then you didn't port forward to your proxy

#

Port forward should be to the proxy, which connects to HA

mellow tinsel
#

im not at home now..more soon I show how my router are configured in the port forwarding

#

I think I have the configuration ok..but..

stoic estuary
#

Problems setting up NGINX for HA

stoic estuary
mellow tinsel
#

in my NGinx config I have configured the port 8126 in HTTPS(SSL) Port

#

in the router:

#

Name of service: HomeAssistant
IP Device: 192.168.0.248 (the ip of the virtual machine)
External port: 443
Internal port: 8126
Protocol: TCP

#

if I delete one of the lines of http the remote access KO!

stoic estuary
#

Well... check the proxy logs, check the HA log

#

And... share your current configuration.yaml

#

And ...

thorn locustBOT
mellow tinsel
#
WARNING:homeassistant.util.yaml.loader:YAML file /config/configuration.yaml contains duplicate key "http". Check lines 23 and 28
ERROR:homeassistant.config:Invalid config for 'template' at template.yaml, line 1: 'template' is an invalid option for 'template', check: template```
stoic estuary
#

Well, that first one I told you about already

#

The second one... you'll have to shae the template.yaml file

thorn locustBOT
#

Please use a code share site to share code or logs, for example:

Please don't use Pastebin, since it can randomly add spaces to the main view. Please also don't share text as images since it makes it harder for people to help you. Remember that others may have colour blindness, impaired vision, etc.

mellow tinsel
#

dont understand what can I do in template to work properly?

stoic estuary
thorn locustBOT
#

Sadly we're not mind readers (any more anyway, not after the last time we tried). Please share the YAML and any errors so we can see what you've done.

mellow tinsel
#

ok..I delete the first line in template.yaml... now work!!!

#

nice!!!!

#

work now! yesterday dont!

#

I delete this:

#
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem```
#

but now the connection is encrypted to? its safe??