James Hodgkinson
James Hodgkinson
> Maybe the server-side encryption with customer-provided keys (SSE-C) will be the easiest way? > > [Using server-side encryption with customer-provided keys (SSE-C)](https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html) that only works if you're using AWS...
Huh, today I learned. Thanks!
If you try starting it with [debug logging turned on](https://kanidm.github.io/kanidm/master/integrations/pam_and_nsswitch/troubleshooting.html?highlight=debug#increase-logging) does `kanidm-unixd` show anything more?
I think this might be some 1.7.1-related things, if you look at [the release notes for 1.7.2/3](https://github.com/kanidm/kanidm/releases/tag/v1.7.3) there's a lot of performance/reliability fixes we've put in place... @Firstyear can you...
Yeah, it is. I'll try and sort that soon.
Sorry, seem to have copied the wrong version from the about page - I have updated the ticket - Home Assistant 2023.5.3 is running.
Nope, I've resorted to provisioning devices by running `esphome` on my laptop then importing it into hass, which is painful.
@DN0000 what was it trying to resolve and failing? It shouldn't be trying to resolve *anything* while providing a file to download?
It looks to relate to this function in tornadoweb: https://github.com/tornadoweb/tornado/blob/6e3521da44c349197cf8048c8a6c69d3f4ccd971/tornado/web.py#L2531 triggered by the lack of a config element... I'm guessing the HASS ingress redirector is messing with it somehow. Running...
Hey, this isn't stale, it's still an issue!