#by just disabling the flag "proxy" on CF

1 messages · Page 1 of 1 (latest)

brisk sun
#

Yes

stiff fossil
#

cool, gonna try it! thanks!

it's weird cuz it works a lot of times, then stop working for a bit and come back working

stiff fossil
#

disabled for a few days now and... yup, does not work
still with the same problem

do you have another idea?

brisk sun
#

What doesn't work?

stiff fossil
#

oh sorry, it's been some time

I'm with the

Unable to connect to Home Assistant.

Retrying in 58 seconds...
Retry now

error

#

My original message:

Hey, everyone!

Can somebody help me with the error "Unable to connect to Home Assistant / Retry"?
I know a lot of people got problems with it, but I can't fix it with the info I found online.

This errors happens randomly when trying to reach the frontend (backend still working, like clicking on widgets on android). After a few tries I can connect to it.

Already disabled https 2 support, disabled ban ip.
I use nginx proxy manager with cloudflare dns and proxy. My domain is from godaddy.

brisk sun
#

What do your proxy logs show? Do they show the connection attempts, or not?

stiff fossil
#

it shows

# 
[15/Jan/2024:11:26:22 +0000] - 200 200 - GET https xxx.com.br "/static/translations/pt-BR-3a694c0b80f0f6d0b6fdb5c075a54c8f.json" [Client xxx] [Length 16459] [Gzip -] [Sent-to 10.0.0.217] "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 OPR/105.0.0.0" "https://xxx.com.br/lovelace"

[15/Jan/2024:11:26:24 +0000] - 404 404 - GET https xxx.com.br "/static/locale-data/intl-displaynames/pt-BR.json" [Client xxx] [Length 14] [Gzip -] [Sent-to 10.0.0.217] "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 OPR/105.0.0.0" "https://xxx.com.br/lovelace"
#

error.log doesn't have anything

brisk sun
#

And does that match all the connection requests?

#

And ... you're not trying to do any URL re-writing?

stiff fossil
#

Uhh, I don't know what this means

Sometimes work nicely, sometimes I got the error (without changing anything). My ha server is 3 yo+, so I'm not developing or anything like that

Abou the url:

I changed the domain about 1 year ago. Before that I've never faced this situation. Maybe I have to clean something on HA?

brisk sun
#

Nah, if it was an HA problem then it'd either never work, or always would

stiff fossil
#

Oh I see

I have another webapps running in this reverse proxy without errors.
It's weird, cuz even when I'm facing the error to reach the lovelace, the proxy still works for backend connections (like widget buttons on android, communication with the app on android and wearos)

brisk sun
#

Separate domain for each?

#

(or port)

stiff fossil
stiff fossil
stiff fossil
#

I just remembered I have crowdsec running. Gonna turn it off for a few days and come back to let you know if solves 😄