My BrewBlox has been up and running for a few months now with the Tilt integrated. I’m on my 3rd fermentation batch and I started getting an error on Chrome and Safari that indicates the location of my BrewPi is “Unsecure” and the browsers wont let me get to the BrewPi. AND, when I go to Options and Security, it wont let me add the site to any “Safe” pages list. In fact there are no options provided to allow me to get to the network location.
Don’t know if it helps, but I also just started getting a “Waiting for Datastore” error as well, when I can get to the location of the BrewPi. Reminds me of the time-out errors with the Arduino version.
I’ve got a couple of shots of the UI on Chrome errors and note that on the site permissions, the areas “greyed” out are not selectable. That’s what seems strange.
Only in Firefox. And when I do, the site just times out. Last Friday, I finished fermenting a Lager and the dashboard loaded just fine thru the entire process.
I started a new fermentation last Friday as well. And it started fine, although I was getting the “Waiting for Datastore” message immediately. Now that doesn’t come up. Just the unsecure error and then the time-out.
brewblox-ctl down
brewblox-ctl makecert
brewblox-ctl up
Then force refresh the UI, and check whether the certificate information changed. The certificate information in chrome should show “issued to: .”, and “issued by: .”.
Short version: SSL certs are required for encrypted (HTTPS) browsing. They are used to prove the identity of the server.
At a guess, the cert file in brewblox/traefik/ got deleted or corrupted. The traefik service will attempt to generate one on the spot, but that leads to the errors you saw.
Edit: you are using http at port 6080? It looks like you updated the http port variable, and browsers will use http 80 unless explicitly told otherwise.
Could you please run brewblox-ctl log? There seems to be something odd going on. Your cert file getting corrupted once is something that can happen, but twice definitely indicates either a bug or a configuration error.