Michael Robbins

Ohh ok so it's actually working end-to-end, just after some time there's error(s). If you've got a user/pass setup then anon auth isn't needed. I've got just a separate mqtt...

I guess that error above is more to do with the MQTT server not being availabe/routable/connectable from solariot..? If it cannot create the socket, that just means roughly "the packets...

If it's in docker can you `exec` into the solariot container and `telnet` to the mqtt IP/port to verify you can manually connect?

Unless someone else has this inverter and willing to give it a shot, you're going to have to 'have a go yourself' as only then can the registers be confirmed...

Nice! I'll stare at mine on the weekend when I get a chance :)

Stick an oauth proxy/authelia/etc before it, that's probably your best way to secure something like that with minimal effort (assuming you have something like this running for other apps)

Is there a way to avoid using the Host OS you think? Possibly with volumes? I guess we can't control how the runner's logic about mounting containers works though? Context:...

We are seeing this exact same thing but with a PROCEDURE that returns a VARCHAR (I don't think that's the problem)... We see the PROCEDURE correctly created, and then it...

Currently setting this label on my `traefik-forward-auth` container: `traefik.http.middlewares.traefik-forward-auth.forwardauth.authResponseHeaders: "X-Forwarded-User"` Results in the correct users email being specified with a default keycloak OIDC setup: `"X-Forwarded-User":["[email protected]"]` Is there any other settings...

Here's a Keycloak script I rigged up that performs RBAC based on Client Roles in keycloak and integrates nicely with Traefik Forward Auth and OIDC. It first verifies the user...