#Nginx help (moving to HAY)

1 messages · Page 1 of 1 (latest)

fast viper
#

[23:11:56] INFO: Running nginx...
nginx: [emerg] unexpected "}" in /share/nginx_proxy_default_fix_ingress.conf:14
[23:11:56] INFO: Service nginx exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service crond: stopping
[23:11:56] INFO: Service crond exited with code 256 (by signal 15)

slate willow
#

Do you see the conf file in /share?

fast viper
#

Yes, the nginx ingress.conf is present

slate willow
#

Can you find an unexpected } within it?

fast viper
#

location /api {
proxy_connect_timeout 60;
proxy_read_timeout 60;
proxy_send_timeout 60;
proxy_intercept_errors off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Host $host:8126;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://homeassistant.local.hass.io:81...
}

slate willow
#

Hmm Doesn't look like it.

fast viper
#

Any other ideas?

slate willow
#

I don't use the add-on, but is that a file you manually created and is referenced in the add-on config?

#

Maybe try deleting it and re-creating it?

fast viper
#

I had to add that otherwise the add-on would break esphome. I have reinstalled the nginx add-on to no success.

slate willow
#

I mean that particular file in /share

fast viper
#

Yes

slate willow
#

is that something which persisted

#

ok

#

oh wait

#

missing a ; on that last line possibly?

#

like all the others

fast viper
#

I can try, but the text is all copy and pasted directly from the same instructions i used last time and verified the config before reboot

#

[12:06:11] INFO: Running nginx...
nginx: [emerg] invalid port in upstream "homeassistant.local.hass.io:81..." in /share/nginx_proxy_default_fix_ingress.conf:13
[12:06:11] INFO: Service nginx exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service crond: stopping
[12:06:11] INFO: Service crond exited with code 256 (by signal 15)

slate willow
#

did that used to be 8123

fast viper
#

No

slate willow
#

well the } error is taken care of. This port is not

#

what is port 81...

#

and how is that valid

fast viper
#

Nginx is doing ssl proxy which is port 80, i assume it is related to that

slate willow
#

directly from the same instructions i used

#

where are these? I can't find reference to this line with a search

#

all other examples i find have an actual port being used wihout ...

fast viper
slate willow
fast viper
#

I will give that a shot. I wonder if the notes changed from when I did the initial system to moving to HAY. Great catch!

slate willow
#

the youtube info mangled the info

#

my screenshot is of the video

#

I don't know why I had to review it for you but...what you have is not what is provided

fast viper
#

What i got is from the info in the video notes

slate willow
fast viper
#

[12:25:26] INFO: Running nginx...
nginx: [emerg] invalid port in upstream "homeassistant.local.hass.io:8123." in /share/nginx_proxy_default_fix_ingress.conf:13
[12:25:26] INFO: Service nginx exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service crond: stopping
[12:25:27] INFO: Service crond exited with code 256 (by signal 15)

#

Removed the extra period, now running stable. Thank you!

#

Remote access restored