I was using client 2.1.16 on my Windows machines. Upgrade to 2.3.1.0 has been offered recently. After the upgrade, client is launched normally, I see the services as usual but actually, communication is not working at all. After reinstalling previous version, everything is ok. Fortunately, for now, this is a testing platform. Are there any requisites before upgrading to this version? At the same time, I also upgraded Mac client and faced no issue.
That's important information. Thank you for letting us know. If you're willing, could you go to the windows version and go to help -> feedback and send the logs and zip file through to help at OpenZiti.io?
You must have a configuration that's triggering a bug and we need to fix that ASAP. Your logs will help us identify where and how.
Do you know what sort of service you have configured that's not working?
That's important information. Thank you for letting us know. If you're willing, could you go to the windows version and go to help -> feedback and send the logs and zip file through to help at OpenZiti.io?
You must have a configuration that's triggering a bug and we need to fix that ASAP. Your logs will help us identify where and how.
Do you know what sort of service you have configured that's not working?
Can you possibly send along your logs and any configuration you have for your overlay, or exactly what isn't working? We will be rolling this release out Monday for everyone, if I don't hear back from you. I shared a PSA type of post showing people how they can disable automatic updates if needed/wanted here: Ziti Desktop Edge for Windows - 2.3.1
Can you possibly send along your logs and any configuration you have for your overlay, or exactly what isn't working? We will be rolling this release out Monday for everyone, if I don't hear back from you. I shared a PSA type of post showing people how they can disable automatic updates if needed/wanted here: Ziti Desktop Edge for Windows - 2.3.1
I have proceeded to Desktop Edge update again, same issue. Please find attached some information, hope it will help. I must go back to previous version, hopefully waiting for a solution ASAP.
Best regards,
(Attachment Ziti Desktop Edge update issue.pdf is missing)
Can you possibly send along your logs and any configuration you have for your overlay, or exactly what isn't working? We will be rolling this release out Monday for everyone, if I don't hear back from you. I shared a PSA type of post showing people how they can disable automatic updates if needed/wanted here: Ziti Desktop Edge for Windows - 2.3.1
Can you possibly send along your logs and any configuration you have for your overlay, or exactly what isn't working? We will be rolling this release out Monday for everyone, if I don't hear back from you. I shared a PSA type of post showing people how they can disable automatic updates if needed/wanted here: Ziti Desktop Edge for Windows - 2.3.1
Thanks for putting this document together. Unfortunately the logs in the PDF don't give us a complete enough picture to diagnose the issue. Could you please go back to 2.3.1 and then from within Ziti Desktop Edge go to Help -> Support. It will generate a zip file that includes logs and other information that will hopefully tell us what's going on. Please email this zip file to help@openziti.io.
Thanks for putting this document together. Unfortunately the logs in the PDF don't give us a complete enough picture to diagnose the issue. Could you please go back to 2.3.1 and then from within Ziti Desktop Edge go to Help -> Support. It will generate a zip file that includes logs and other information that will hopefully tell us what's going on. Please email this zip file to help@openziti.io.
Looking at the logs, it appears as though the process is either crashing or being terminated over and over again by something like a virus scanner/endpoint protection. It's really quite bizzare and I've never seen this behavior before. It makes me think something else is happening that's... Strange.
Could you please enable debug logging by going to help -> advanced settings -> Set Logging Level to Debug and then share the logs again?
I actually see TRACE logs in other logs. And actually, could you reboot this machine before you do that? It seems like there's another ziti-edge-tunnel running? Something seems really strange here.
I actually see TRACE logs in other logs. And actually, could you reboot this machine before you do that? It seems like there's another ziti-edge-tunnel running? Something seems really strange here.
I actually see TRACE logs in other logs. And actually, could you reboot this machine before you do that? It seems like there's another ziti-edge-tunnel running? Something seems really strange here.
Thanks for the latest logs. Here's what we can see from them:
The controller version that you're running, 0.32.2, has a known issue that prevents more recent tunnelers from being able to host services.
There are what look like signs of the tunneler process (ziti-edge-tunnel.exe) exiting or perhaps being killed, but it's hard to know exactly what's happening or why. All we can see is that the process restarts with no messages about being closed/exiting cleanly. Now that you've set the log level to debug, this will be easier to diagnose if it turns out to persist after the controller is upgraded.
So I think the next step is to update your controller to 1.0.0. Let us know if we can help with that.
Thanks for the latest logs. Here's what we can see from them:
The controller version that you're running, 0.32.2, has a known issue that prevents more recent tunnelers from being able to host services.
There are what look like signs of the tunneler process (ziti-edge-tunnel.exe) exiting or perhaps being killed, but it's hard to know exactly what's happening or why. All we can see is that the process restarts with no messages about being closed/exiting cleanly. Now that you've set the log level to debug, this will be easier to diagnose if it turns out to persist after the controller is upgraded.
So I think the next step is to update your controller to 1.0.0. Let us know if we can help with that.