Hi Michele, On Fri, 7 Mar 2025 at 18:02, Michele Salerno <[email protected]> wrote:
> I have no doubt that the instances updated by you have no problems, > being the developers you know where to intervene for any problem. > That doesn't mean anything, we also incur into issues from time to time. If there was a bug like the one you are describing we would have noticed, so what I am trying to say is that it is most likely a misconfiguration, unless you can provide instructions on replicating the bug you're having. > Redis runs locally, why the DNS resolution if it is in localhost? > Redis is installed from the ansible playbook of openwisp. > Indeed the resolution is not the issue, the log points out the system can't connect to redis. > Anyway I was just asking how to debug openwisp. > On routers with OpenWrt 23.05.4 I had no problems, now I have continuous > up and down problems. With the update done with ansible-openwisp2 > something has changed. > As you should know, the ansible role does not touch the configuration of your management VPN. > I tried installing wireguard, it does the same thing with wireguard as > well. > Is the ping check hallucinating and inventing bad results? Or are there real VPN stability issues? Assuming you backed up your system before upgrading, in the worst case scenario you could go back there. F. -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion, visit https://groups.google.com/d/msgid/openwisp/CAAGgX6JcQYfCJwtyGBRGsn_i_V67MMH-4x4hsD2ZY_i-GwNA4Q%40mail.gmail.com.
