sholdee
sholdee
> I don't think I can control that in the blocky config I set forward_ip, recreated my pods from the tagged v0.8.1 release, set forward_blocky again after they all finished,...
> I don't think I can control that in the blocky config I did some more testing and gathered some more logs. It seems the issue was actually that the...
Rolled cluster back to v0.7.0 and cleared out all records in root zone. The 2 example domains posted above now resolve as expected: https://pastebin.com/raw/Fhv7TXzk Config in all test cases: ```...
I created a venv under /opt/RPi-Reporter-MQTT2HA-Daemon, activated the venv, installed requirements, and set isp-rpi-reporter.service as such: ``` WorkingDirectory=/opt/RPi-Reporter-MQTT2HA-Daemon/ ExecStart=/opt/RPi-Reporter-MQTT2HA-Daemon/venv/bin/python3 -u /opt/RPi-Reporter-MQTT2HA-Daemon/ISP-RPi-mqtt-daemon.py ``` Has been working great. I prefer having it...
> Hey @sholdee, > > Do you have more log output to debug indicating the bouncer shutting down (or similar), ~and are there other modules in your custom Caddy build~?...
Thank you for looking into this. I tried the workaround suggested by @shindouj and set `CADDY_DOCKER_EVENT_THROTTLE_INTERVAL` to 2s, and this seems to have resolved the issue. I didn't try any...
Same errors "Failed to find local environment" here after update from 2.21.2 to 2.22.0, although I am still able to connect to and control my agents. Removing and adding back...
In my case, I don't even have a local environment. I am running portainer-ce in Kubernetes and only connecting to a portainer agent to control a standalone docker instance. I...
> Hi all, I am going to look into replicating this and raising with the team. The error can be replicated by having at least 1 environment configured and no...
> Adding a local (socket) environment fixed it for me. Previously there was just an a agent environment connected. This is true, but it should not be necessary to mount...