subito
subito
I see the same issue on FreeBSD, version: r2.13.4-1. But with a slightly different error: `Storing icinga_command_argument[] failed: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'argument_name' cannot be null` Any progress...
Of course, just catching the error would be great. As you said: Any sort of queue-and-retry should be handled on a mailserver. But panicing on a simple SMTP-Error is probably...
Having the same issue since a few updates ago. First time it happend was 2023.11.1 -> 2023.11.3, and now the latest update to 2023.12 also triggered this. Most Integrations fail...
The problem still persists. If I disable some integrations before an update, the update works fine. I can't enable the integrations afterwards, it takes a few hours until I can...
The same symptoms and similar logs. From what I understand an upgrade with HAOS downloads a new core and swaps it in place. I have the same problem that homeassistant...
I'm facing the same problem. I tried the solution mentioned in #2505: https://www.authelia.com/integration/openid-connect/openid-connect-1.0-claims/#restore-functionality-prior-to-claims-parameter, but using the `claims_policy` just gives me the same error. Not using the `claims_policy` lets me login,...
Thats a super helpful hint, thank you! Digging into my schema I found that it had some migrations missing, too! Unfortunately its not easy to find out which those are...
I got it working again by manually fixing the entries in the `users` table. Setting `provider_identifier` to the identifier I found in the Authelia-Logs and `provider` to `oidc` like this:...
Here is my `status 8` output: ``` 08:51:57.771 CMD: status 8 08:51:57.779 MQT: stat/tasmota_B7FAC0/STATUS8 = {"StatusSNS":{"Time":"2024-03-06T08:51:57","SM":{"1_8_0":7555000.000,"1_8_1":0.000,"1_8_2":0.000,"2_8_0":0.00000000,"16_7_0":0.00,"36_7_0":0.00,"56_7_0":0.00,"76_7_0":0.00,"96_1_0":"XXXXXXXXX"}}} ``` I'm currently working around this issue by creating a sensor that maps to...
This issue is still relevant