#It seems that /config/ does seem to not

1 messages · Page 1 of 1 (latest)

stone bear
#

Locally once you add SSL you have to use https://

jovial willow
#

That...makes a lot of sense. I suppose throwing my head against the wall over the config files made me oblivious to other things. I feel dumb if that's all it is. I'll definitely try when I get home, thanks!

stone bear
#

The "work around" is to use a proxy for SSL

jovial willow
#

/config was indeed the right folder. I don't understand how considering file editor shows /homeassistant but if it works then it works. I can access it both locally and remotely now which is awesome, although there seems to be an issue with the certificate. I'm not sure if you'd have time to help or if I should just make a new post on the main thread. if you go to https://name548-gaming.com you get a msg saying not secure, but then you can click "certificate not valid" and it literally shows the certificate so idk the issue. If you do it on mobile it shows: https://postimg.cc/JDkb8nyf

#

An error occurred when building the chain for this certificate. The certificate might lack necessary metadata or its certificate authority might be malfunctioning. Details:

  • The chain contains an untrusted certificate without standard CA issuer information (subject = "O="CloudFlare, Inc.", OU=CloudFlare Origin CA, CN=CloudFlare Origin Certificate"; issuer = "C=US, O="CloudFlare, Inc.", OU=CloudFlare Origin SSL Certificate Authority, L=San Francisco, ST=California"; error code = 20)
#

i'm just newer to the networking side of things and I'm not sure what to make of it

#

I got my cert from cloudflare by clicking ssl/tsl -> origin -> create and then I downloaded both the origin.pem and the privkey.pem and I put them in the home assistant config folder

jovial willow
#

nevermind, I figured it out. I needed to proxy my DNS and then add the list of cloudflare proxies to my HA config

#

it all works now, thanks for the help!

stone bear
#

/config was indeed the right folder. I don't understand how considering file editor shows /homeassistant but if it works then it works.
That's a recent change for the way that some add-ons behave, and it's caused confusion

jovial willow
#

I currently don't need to access anything in the folder, but just for future reference, say I wanted to access a folder or file one level before the /config folder. File editor shows /homeassistant which is all there is. PowerISO allows me to see the whole virtual drive and I can see other files and folders aside from /homeassistant, one being an SSL folder. In theory, if I wanted to keep my SSL/TSL keys in that folder, what would the file path be? PowerISO shows it as the supervisor folder (hence why earlier I was trying /supervisor/homeassistant. So if /config = /homeassistant what does /supervisor equal?

#

if that makes any sense lol