is there a version of the app I can help test that works with the new ziti user/socket?

[qrkourier]

I'm trying to use the app with the new ziti user that's created by the DEB/RPM install package. It shows ZET isn't running and I guess it's because it doesn't yet know about the new IPC socket location. I tried latest release and a local build of main branch.

[JeremyTellier]

If you pull the latest repo and build it locally it is changed to the /tmp/ ipc path. I will make a release ASAP.

[qrkourier]

Cool, thanks @JeremyTellier ! I'll come back to it after the start script is re-added to package.json.

[qrkourier]

@JeremyTellier I ran

npm install --no-save && npm start

in src dir on main branch, but the UI app still says

error:  Error: connect ENOENT /tmp/ziti-edge-tunnel-event.sock
    at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1187:16) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'connect',
  address: '/tmp/ziti-edge-tunnel-event.sock'
}

This is where it's actually located:

$ ll /tmp/.ziti
total 0
srwxrwxrw- 1 ziti ziti 0 Mar 22 11:13 ziti-edge-tunnel.sock=
srwxrwxrw- 1 ziti ziti 0 Mar 22 11:13 ziti-edge-tunnel-event.sock=

[JeremyTellier]

@scareything - Should that path be working on what @qrkourier has for a tunnel?

/tmp/ziti-edge-tunnel-event.sock

[qrkourier]

I thought the desktop UI was going to start using this new path to the socket.

I'm running pre-release build of ZET for testing.

❯ /opt/openziti/bin/ziti-edge-tunnel version
v0.20.23-17-g5574f48-local

I downloaded the DEB from GH Actions after we merged the PR that changed the socket location.